Status dot merged and deployed on all three Satsuma websites
Satsuma's main site, its block explorer and this engineering site now each carry a small status indicator, a dot that reads a status response. The change to each of the three sites was squash-merged and deployed, and all three deploys succeeded.
On the explorer, the dot now reads the response with the explorer's existing status parser instead of keeping its own copy. The explorer change had to be rebased first, after other changes merged ahead of it and caused conflicts, and it was re-checked in a browser at phone width before merging. Its status link sits after the new network and satsuma.one links. The explorer's check, build and tests pass.
The engineering site's change merged with a red CI check. "Its CI check was red, but only because the GitHub org's artifact storage is full. The build itself passed, and the deploy job doesn't upload artifacts." The local worktrees and branches used for the work were removed afterwards.
The live pages on all three sites include the dot, confirmed from the deployed HTML rather than by opening each site in a browser. The full artifact storage is still open and still turns the engineering site's CI red.
- Rebased the explorer change onto the main line after other merged changes caused conflicts
- Re-checked the explorer change in a browser at phone width before merging
- The explorer's status link goes after the new network and satsuma.one links
- The engineering site's change was merged despite a red CI check, because the cause was full artifact storage while the build itself passed and the deploy job uploads no artifacts
- The live sites were checked through their deployed HTML, not each opened in a browser
- The GitHub organisation's artifact storage is full, which turns the engineering site's CI check red