Skip to content

ci: merge-back pushes directly to beta via GitHub App#489

Merged
steilerDev merged 5 commits intobetafrom
ci/smarter-change-detection
Mar 6, 2026
Merged

ci: merge-back pushes directly to beta via GitHub App#489
steilerDev merged 5 commits intobetafrom
ci/smarter-change-detection

Conversation

@steilerDev
Copy link
Owner

Summary

  • Replace the merge-back PR (main → beta after stable release) with a direct merge+push using the cornerstone-bot app token
  • Eliminates the manual step of merging the sync PR after every stable release

Test plan

  • Verify next stable release automatically merges main back into beta without creating a PR

🤖 Generated with Claude Code

claude added 5 commits March 6, 2026 10:40
…t hook

- Remove `ci` output from detect-changes and all downstream conditions.
  Workflow-only PRs no longer trigger the full pipeline (~20+ runner-minutes
  saved). Dockerfile/.nvmrc are covered by `app`, e2e/ by `e2e`.
- Change DOCKERHUB_USERNAME from secrets to vars in ci.yml and release.yml
  (usernames are not sensitive and belong in repository variables).
- Remove pre-commit hook (typecheck runs in CI quality gates).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Auto-fix workflow now commits and pushes directly to beta instead of
  creating a PR. The github.actor guard prevents infinite loops.
- Remove husky and lint-staged dependencies — no longer needed since
  pre-commit hook was removed and validation runs in CI.
- Drop pull-requests write permission (no longer creating PRs).

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Use a dedicated GitHub App (cornerstone-bot) instead of github-actions[bot]
to push auto-fix commits to beta. This allows scoping the branch protection
bypass to only this app, rather than giving blanket bypass to all Actions.

Setup required:
- Create GitHub App with Contents: Read & Write permission
- Store App ID as vars.BOT_APP_ID, private key as secrets.BOT_PRIVATE_KEY
- Add only this app to beta's ruleset bypass list

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Quality Gates now depends on all jobs (static-analysis, test, docker,
e2e-warmup, e2e-smoke, e2e, e2e-merge-reports) and always runs. It
accepts skipped results but fails on any failure/cancellation.

Docker PR Release now only runs after Quality Gates passes.

This ensures the Quality Gates required check always reports a status,
making PRs mergeable even when upstream jobs are skipped.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Replace the merge-back PR with a direct merge+push using the
cornerstone-bot app token. This eliminates the manual step of
merging the sync PR after every stable release.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@steilerDev steilerDev merged commit a07c87b into beta Mar 6, 2026
11 checks passed
@github-actions
Copy link
Contributor

github-actions bot commented Mar 6, 2026

🎉 This PR is included in version 1.12.0-beta.49 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants