Repository navigation
Conversation
jayleaton
force-pushed
the
scratch/foundation-shape-after-gomod
branch
from
October 22, 2026 11:18
cb1f56f to
417a41f
Compare
jayleaton
marked this pull request as ready for review
October 22, 2026 11:18
jayleaton
force-pushed
the
scratch/foundation-shape-after-gomod
branch
2 times, most recently
from
October 22, 2026 11:33
a8d2e53 to
6675742
Compare
jayleaton
force-pushed
the
scratch/foundation-shape-after-gomod
branch
from
October 22, 2026 11:36
6675742 to
ee5479a
Compare
jayleaton
added a commit
that referenced
this pull request
Nov 1, 2026
make pr-merge ARGS="--check-deploy <sha>" read only GitHub's Deploy staging runs, so with Actions disabled it always failed, even for a commit deployed by hand with make railway-up. With no Deploy staging run for the commit, it now asks Railway (railway CLI, read only) for the newest staging deployment of web and admin: PASS only when both are SUCCESS with the message "make railway-up <that commit>" and both /healthz (STAGING_WEB_URL, STAGING_ADMIN_URL) answer 200 ok (verify.StagingFromRailway). A deployment that records no commit is "cannot tell", never a pass. The project is RAILWAY_PROJECT_ID, else deploy/platform.yaml's project (auto: the GitHub repository's name). make railway-up now gives that message: "make railway-up <commit>" for a clean checkout, "make railway-up (uncommitted changes on <commit>)" otherwise. Railway's deployment metadata holds no commit for a railway up upload, and the image has no git data, so the message is the record. Proven in sparkrack (#65). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jayleaton
added a commit
that referenced
this pull request
Nov 1, 2026
#148) make pr-merge ARGS="--check-deploy <sha>" read only GitHub's Deploy staging runs, so with Actions disabled it always failed, even for a commit deployed by hand with make railway-up. With no Deploy staging run for the commit, it now asks Railway (railway CLI, read only) for the newest staging deployment of web and admin: PASS only when both are SUCCESS with the message "make railway-up <that commit>" and both /healthz (STAGING_WEB_URL, STAGING_ADMIN_URL) answer 200 ok (verify.StagingFromRailway). A deployment that records no commit is "cannot tell", never a pass. The project is RAILWAY_PROJECT_ID, else deploy/platform.yaml's project (auto: the GitHub repository's name). make railway-up now gives that message: "make railway-up <commit>" for a clean checkout, "make railway-up (uncommitted changes on <commit>)" otherwise. Railway's deployment metadata holds no commit for a railway up upload, and the image has no git data, so the message is the record. Proven in sparkrack (#65). Co-authored-by: JJ Eaton <58495321+oldbettie@users.noreply.github.com> Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Scratch; will be closed.