Feat: Track deploys in a production environment #73
+67
−28
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Move the deploy steps out of the checks job into a deploy job that runs after it on pushes to main. The job belongs to the GitHub environment "production", so the repository lists each deploy, the live commit and a link to the site. The new job starts from a fresh checkout, so it installs and builds again. Pull requests still only run checks, which keeps its name for branch protection. The site check now also runs a sightings query, since health does not touch the database and a wrong database password passed the old check. Rename the workflow to ci-cd.yml and "CI/CD" now that it also deploys. Document the deploy job, the environment and the "Access denied" fix in docs/ci-cd.md. Closes #72 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Closed
asgeija
approved these changes
Oct 15, 2026
Sign in
to join this conversation on GitHub.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Move the deploy steps out of the checks job into a deploy job that runs after it on pushes to main. The job belongs to the GitHub environment "production", so the repository lists each deploy, the live commit and a link to the site. The new job starts from a fresh checkout, so it installs and builds again. Pull requests still only run checks, which keeps its name for branch protection.
The site check now also runs a sightings query, since health does not touch the database and a wrong database password passed the old check.
Rename the workflow to ci-cd.yml and "CI/CD" now that it also deploys. Document the deploy job, the environment and the "Access denied" fix in docs/ci-cd.md.
Closes #72