Skip to content

docs: require a master->develop merge back after every release tag - #280

Merged
flupkede merged 1 commit into
developfrom
docs/release-merge-back
Sep 21, 2026
Merged

flupkede merged 1 commit into
developfrom
docs/release-merge-back

Conversation

@flupkede

Copy link
Copy Markdown
Owner

Adds step 4 to RELEASING.md plus a matching rule.

Squash-only release commits leave master and develop without shared history, so the next release PR is three-way merged against a pre-squash ancestor. Files added since then look independently added on both sides; git auto-resolves that only while the blobs stay byte-identical, which is why releases merged cleanly for months and then v1.4.4 hit phantom conflicts on resident.rs (its first edit since introduction).

The merge back is already done for v1.4.4 (422d07d) — master is now contained in develop again.

Squash-only release commits leave master and develop without shared
history, so the next release PR is three-way merged against a
pre-squash ancestor and reports phantom add/add conflicts as soon as a
file added since then is edited (hit on v1.4.4).
@flupkede
flupkede merged commit d4c6482 into develop Sep 21, 2026
2 of 3 checks passed
@flupkede
flupkede deleted the docs/release-merge-back branch September 21, 2026 10:51
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