Repository navigation
docs: the fork-rebase runbook, and the release prerequisites named where callers read - #6
Merged
Merged
Conversation
…ere callers read - docs/fork-rebase.md: the IntraVox rebase (instalador #35) written down as the road every fork app takes — the pre-rewrite twin, the per-path merge policy, the reconciliation commit, the regenerate-last order, the zero-deletions verification, and the force-push-then-PR flow. eurooffice and desktop_workspace are next. - app-release.yml's header names what a calling repo needs before its first tag: the release environment with the two secrets, the v* tag ruleset, and a pin that points at a commit on the default branch.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Cierra #4, cierra #5 (retro of instalador #35).
What & why
docs/fork-rebase.md(Retro #35: falta el runbook de rebase de fork — el próximo fork vuelve a derivar todo el procedimiento #4) — the IntraVox rebase procedure, improvised once and now written down: the pre-rewrite twin (rebase --skipfor the duplicate), the per-path merge policy (bundles → theirs; ratchets and l10n manifests → regenerate at the end; everything else by hand with both-sides constructor merges), the reconciliation commit pattern, the regenerate-last order, the four-gate verification with the zero-deletions diff against the backup ref, and the force-push-main-then-PR flow. Two more fork rebases (eurooffice, desktop_workspace) are waiting in #27's P2.app-release.ymlheader (Retro #35: los prerrequisitos de publicación (entorno release, secretos, ruleset de tags) no están escritos en ningún lado #5) — one comment block naming what a calling repo needs before its firstv*tag: thereleaseenvironment with both secrets, thev*tag ruleset, and a default-branch pin (the local-only-SHA failure mode that cost the #35 session five API calls). Comment-only; existing SHA pins are untouched.IntraVox's AGENTS.md already points at the runbook (APS-Conecta/IntraVox#19).
AI involvement
Written with AI assistance (Claude Code + pi).