Conversation
Document the dev → PR → main loop, commit hygiene, and the post-merge `git merge origin/main` resync to keep dev from drifting. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The snapshot Action pushed roadmap.json straight to main, which the
branch ruleset rejects ("changes must be made through a pull request"),
so every issue event failed and emailed. The server route already does
the job (server-side fetch, no exposed token, cached) — so remove the
redundant workflow, script, and static file and read the route directly.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
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
1 participant
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.
What
Removes the
roadmap-snapshotworkflow, its script, and the committedweb/public/roadmap.json. Reverts the/roadmappage to read the existing/api/roadmapserver route.Why
The snapshot Action pushed
roadmap.jsondirectly tomain, which the branch ruleset rejects (changes must be made through a pull request). So it failed on every issue event and sent failure emails. The existing server route already fetches issues server-side (no exposed token, cached), making the snapshot redundant.Tested
/roadmapverified loading 10 issues via/api/roadmapin preview, no console errorsnext buildruns in CI on this PR