Repository navigation
Conversation
Pushing new `vN.x` and `vN.x-staging` branches to the repository is rejected by the "Require linear history" ruleset, because branch creation evaluates the whole history and `main` still contains merge commits from 2015. Document that a repository admin must disable the rule, push the branches, and enable it again, as done for v26.x and v27.x. Refs: nodejs/Release#1187 Signed-off-by: RafaelGSS <rafael.nunu@hotmail.com>
Collaborator
|
Review requested:
|
7 of 9 tasks
panva
approved these changes
Oct 27, 2026
richardlau
approved these changes
Oct 27, 2026
RafaelGSS
added
author ready
UlisesGascon
approved these changes
Oct 27, 2026
legendecas
approved these changes
Oct 27, 2026
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.
Pushing new
vN.xandvN.x-stagingbranches to the repository is rejected by the "Require linear history" ruleset, because branch creation evaluates the whole history andmainstill contains merge commits from 2015.Refs: nodejs/Release#1187