Skip to content

docs: say that moving main-digdir marks the sync pull request merged - #3

Merged
martinothamar merged 1 commit into
main-digdirfrom
docs/sync-pr-marked-merged
Oct 25, 2026
Merged

martinothamar merged 1 commit into
main-digdirfrom
docs/sync-pr-marked-merged

Conversation

@martinothamar

Copy link
Copy Markdown

Summary

A synchronization lands by moving main-digdir to the approved sync branch with git push --force-with-lease. Step 6 of MAINTAINING-digdir.md now also says:

  • Never use the sync PR's merge button. It would replay the rebuilt queue onto the old main-digdir.
  • Once main-digdir points at the sync branch's head, GitHub marks the PR as merged by itself, so don't close or merge it.

digdir/microsandbox#5 says the same in the Microsandbox runbook.

Evidence

Documentation only. The 0.7.8 synchronization landed this way: #1 shows as merged, without its merge button having been used.

A synchronization lands by moving main-digdir to the sync branch, never
through the pull request's merge button, which would replay the rebuilt
queue onto the old main-digdir. GitHub then marks the pull request as
merged by itself, so it must not be closed or merged by hand.
@martinothamar
martinothamar merged commit 2a4f6ca into main-digdir Oct 25, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant