Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
martinothamar merged 1 commit into from
Oct 25, 2026
Merged

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion MAINTAINING-digdir.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,9 @@ Do this before the Microsandbox synchronization, because its submodule pins the
changes](CONTRIBUTING-digdir.md#checking-kernel-configuration-changes)).
5. Disable workflow files that upstream added (see [Upstream workflows](#upstream-workflows)).
6. After approval, make sure every commit a published runtime still uses is tagged, then move the branch with
`git push --force-with-lease=main-digdir:<old-tip> origin sync/libkrunfw-X.Y.Z:main-digdir`.
`git push --force-with-lease=main-digdir:<old-tip> origin sync/libkrunfw-X.Y.Z:main-digdir`. Never use the sync
pull request's merge button, which would replay the rebuilt queue onto the old `main-digdir`. Once `main-digdir`
points at the sync branch's head, GitHub marks the pull request as merged by itself. Don't close or merge it.

## Tags and corresponding source

Expand Down