Repository navigation
ci(release): sync the open release with main through a PR - #141
Closed
djessyczaplicki-genomcore wants to merge 1 commit into
Closed
djessyczaplicki-genomcore wants to merge 1 commit into
djessyczaplicki-genomcore wants to merge 1 commit into
Conversation
Every push to main (docs/ tickets, hotfixes) opens a PR from main into the newest release/YYYY-MM-DD branch when the release is behind main, unless one is already open or that release has already been merged into main. The Release Guard ruleset blocks direct pushes to release/**, so the sync goes through a PR with the usual approval and checks.
Contributor
Author
|
Sustituida por #142: va directa a main como hotfix 0.18.1. |
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.
Qué hace
Nuevo workflow
Sync release with main(.github/workflows/sync-release.yml). En cada push amain(y a mano con Run workflow):release/AAAA-MM-DDmás reciente.main, si ya contiene todo lo demain, o si ya hay una PRmain → releaseabierta (esa PR se actualiza sola con cada push amain).main → release/AAAA-MM-DD.Por qué una PR y no un push directo
El ruleset Release Guard exige PR con 1 approval y checks verdes en
release/**, así que el bot no puede hacer push. Con la PR, lo que llega demainpasa por los mismos checks que el resto de la release.A tener en cuenta
maindivergen y la siguiente PRrelease → mainda conflictos.GITHUB_TOKENno lanzan otros workflows. Si no aparecen los checks, hay que cerrar y reabrir la PR. Con el siguiente push amainse lanzan solos.main, es decir, tras publicar esta release.main → release/2026-11-17con los 2 tickets dedocs/mergeados enmaindesde ayer.🤖 Generated with Claude Code