Conversation
- Triggers on push to sandbox (i.e. whenever a PR merges into it) - Runs npm ci + npm run build as the required gate; lint is informational only - If the build passes and sandbox has new commits, opens (or updates) a sandbox -> main PR summarizing what's being promoted, and requests review from the repo owner as the notification - Never merges the PR itself - a human must review and merge manually Co-authored-by: Thomas Bohn <bohn.tl@gmail.com>
…log-sync - New rule documents the mostly-automated promotion flow (CI validates the build and opens a human-reviewed sandbox -> main PR) plus a manual fallback and guardrails (never auto-merge, never push directly to main) - medium-blog-sync now notes that its PR should target sandbox, and that production promotion is handled by the new rule/workflow afterward Co-authored-by: Thomas Bohn <bohn.tl@gmail.com>
…rkflow Root cause of the failed run on PR #28's merge: GitHub Actions is not permitted to create pull requests in this repo (Settings > Actions > General > Workflow permissions > 'Allow GitHub Actions to create and approve pull requests' is disabled by default). - Detect that specific GraphQL error and open/update a tracking GitHub Issue with the exact remediation steps, instead of failing silently in the logs - Add the same notify-on-failure/auto-resolve-on-success pattern for build failures (separate tracking issue) - Support an optional PROMOTION_PR_TOKEN repo secret (PAT) as a drop-in alternative to enabling the repo-wide Actions permission - Restructure the pr create/update error handling so 'set -e' doesn't abort before the failure can be captured and reported Co-authored-by: Thomas Bohn <bohn.tl@gmail.com>
Explains the two tracking-issue failure modes (build failed, PR create/update failed), the auto-close-on-success behavior, and the specific repo setting that needs to be enabled for automated PR creation to work. Co-authored-by: Thomas Bohn <bohn.tl@gmail.com>
…e-path-63ac Fix promotion workflow PR-creation failure + add failure-notification path
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
2 participants
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.
Sandbox validated and ready for production
This PR was opened automatically after
sandboxwas validated bythis workflow run.
npm run build): passed04f06f7c6b9d38650bd2f68e742991d5b11acbb8Commits included in this promotion
Review checklist
This PR requires manual human review and must be merged by a person.
This automation will never merge it.