-
Notifications
You must be signed in to change notification settings - Fork 113
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.
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
feat(cli): prompt user when landing PR with several commits #572
Conversation
Codecov Report
@@ Coverage Diff @@
## main #572 +/- ##
=======================================
Coverage 82.57% 82.57%
=======================================
Files 35 35
Lines 1750 1750
=======================================
Hits 1445 1445
Misses 305 305 Continue to review full report at Codecov.
|
a54cebd
to
e419f7b
Compare
--oneCommitMax
option--oneCommitMax
option
e419f7b
to
4c55189
Compare
--oneCommitMax
option
The current commit-queue passes in |
Not sure that's true, I think Lines 71 to 73 in 3e8b07d
|
In which case this is very misleading node-core-utils/components/git/land.js Lines 53 to 58 in 62b3fef
|
And add an option to abort the session if trying to land more than one commit. Refs: nodejs/node#40436
aafb60d
to
cbcf4b0
Compare
Just tried with:
Footnotes
|
Most PRs are meant to be squashed in one commit when landing. If the collaborator hasn't been using `fixup!` commit, the CQ will land the PR as several commits. This change makes the CQ abort by default when attempting to land several commits, unless there's another label added to the PR to force squashing or landing as several commits. Fixes: nodejs#40436 Refs: nodejs/node-core-utils#572
Most PRs are meant to be squashed in one commit when landing. If the collaborator hasn't been using `fixup!` commits, the CQ lands the PR as several commits. This change makes the CQ abort by default when attempting to land several commits, unless there's another label added to the PR to force squashing or landing as several commits. Fixes: nodejs#40436 Refs: nodejs/node-core-utils#572
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: Michaël Zasso <targos@protonmail.com>
Most PRs are meant to be squashed in one commit when landing. If the collaborator hasn't been using `fixup!` commits, the CQ lands the PR as several commits. This change makes the CQ abort by default when attempting to land several commits, unless there's another label added to the PR to force squashing or landing as several commits. Fixes: nodejs/node#40436 Refs: nodejs/node-core-utils#572 PR-URL: nodejs/node#40577
Most PRs are meant to be squashed in one commit when landing. If the collaborator hasn't been using `fixup!` commits, the CQ lands the PR as several commits. This change makes the CQ abort by default when attempting to land several commits, unless there's another label added to the PR to force squashing or landing as several commits. Fixes: nodejs/node#40436 Refs: nodejs/node-core-utils#572 PR-URL: nodejs/node#40577
Most PRs are meant to be squashed in one commit when landing. If the collaborator hasn't been using `fixup!` commits, the CQ lands the PR as several commits. This change makes the CQ abort by default when attempting to land several commits, unless there's another label added to the PR to force squashing or landing as several commits. Fixes: nodejs#40436 Refs: nodejs/node-core-utils#572 PR-URL: nodejs#40577
Most PRs are meant to be squashed in one commit when landing. If the collaborator hasn't been using `fixup!` commits, the CQ lands the PR as several commits. This change makes the CQ abort by default when attempting to land several commits, unless there's another label added to the PR to force squashing or landing as several commits. Fixes: #40436 Refs: nodejs/node-core-utils#572 PR-URL: #40577 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Most PRs are meant to be squashed in one commit when landing. If the collaborator hasn't been using `fixup!` commits, the CQ lands the PR as several commits. This change makes the CQ abort by default when attempting to land several commits, unless there's another label added to the PR to force squashing or landing as several commits. Fixes: #40436 Refs: nodejs/node-core-utils#572 PR-URL: #40577 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
Most PRs are meant to be squashed in one commit when landing. If the collaborator hasn't been using `fixup!` commits, the CQ lands the PR as several commits. This change makes the CQ abort by default when attempting to land several commits, unless there's another label added to the PR to force squashing or landing as several commits. Fixes: #40436 Refs: nodejs/node-core-utils#572 PR-URL: #40577 Reviewed-By: Michaël Zasso <targos@protonmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com>
The idea would be to run CQ with this flag by default, potentially we could add additional labels such as
commit-queue-fixupAll
andcommit-queue-more-than-one-commit
to let the CQ handle more complex PRs.Refs: nodejs/node#40436