You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Move release flow to PR-based and add CODEOWNERS for branch protection (#649)
* Move release flow to PR-based and add CODEOWNERS for branch protection
- Add .github/CODEOWNERS
- Cut a release branch in release.sh and open two PRs (sync to dev,
release to main) instead of merging dev into main locally
- Move tag creation into a workflow that fires on push to main
- Skip auto_version_dev when Config.xcconfig was changed in this push,
so merging the release sync-PR into dev does not double-bump
* Make workflow guards portable via fork check
Replace the hardcoded 'loopandlearn' owner check in workflows with a
fork check, so the workflows run on any non-fork repository (including
a test org) while still skipping on contributor forks.
* Allow skipping sister repo updates in release.sh
Set SKIP_SISTER_REPOS=1 to bypass the LoopFollow_Second / LoopFollow_Third
update_follower steps. Default behavior is unchanged: both sister repos
are updated as today and missing directories still cause a hard error,
so a forgotten clone in production fails fast.
* Revert "Allow skipping sister repo updates in release.sh"
This reverts commit c2792b8.
* Skip patch hunks for files missing from sister repos
Sister repos (LoopFollow_Second / LoopFollow_Third) are intentionally
stripped of dev-only files like release.sh, auto_version_dev.yml,
lint.yml, and warn_main_pr.yml. Any release patch that touches one of
those files used to abort the sister-repo update with 'No such file or
directory'. Now update_follower runs git apply --check first, parses
the missing-file errors, and re-applies with --exclude for each, so the
sister patch covers the files that actually exist.
* Revert "Skip patch hunks for files missing from sister repos"
This reverts commit 45b9871.
--body "Syncs the v${new_ver} version bump from the release branch back to \`dev\` so subsequent auto-bumps on \`dev\` continue from the released minor.
146
+
147
+
\`auto_version_dev\` detects that \`Config.xcconfig\` was changed in this push and skips re-bumping.
148
+
149
+
⚠️ **Use rebase-merge** (not squash or merge-commit) so \`dev\` and \`main\` end up at the same commit SHA after the release."
0 commit comments