Skip to content
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

dev-cmd/bump*: do not allow forcing multiple PRs. #16664

Merged
merged 1 commit into from
Feb 16, 2024
Merged

Conversation

MikeMcQuaid
Copy link
Member

If there are duplicate PRs: we shouldn't suggest and allow a trivial override. Instead, they should be created manually.

An undocumented override exists for BrewTestBot to do autobumps.

MikeMcQuaid added a commit to Homebrew/homebrew-core that referenced this pull request Feb 15, 2024
After/if Homebrew/brew#16664 is merged, this
is needed for `autobump` to open PRs that may be detected as duplicates.
If there are duplicate PRs: we shouldn't suggest and allow a trivial
override. Instead, they should be created manually.

An undocumented override exists for BrewTestBot to do autobumps.
@MikeMcQuaid MikeMcQuaid merged commit eebd844 into master Feb 16, 2024
26 checks passed
@MikeMcQuaid MikeMcQuaid deleted the bump_no_force branch February 16, 2024 08:29
@Porkepix
Copy link

If there are duplicate PRs: we shouldn't suggest and allow a trivial override. Instead, they should be created manually.

An undocumented override exists for BrewTestBot to do autobumps.

What about regular false positives though? Every now end then I sometimes used it because the command detected PRs with just the formula name in it as a duplicate when those PRs were unrelated because either about others formulas referencing that one, either some PR to modify it but that wasn't a version bump and not close to be merged (eg. adding a build option, adding documentation and so on) and while this other PR was either discussed or stalled with no one taking care of it for now, there's no reason to delay the version bump, right?

(Note, the detection could also match both the formula name and the version, which doesn't seems to be the case currently?)

@MikeMcQuaid
Copy link
Member Author

What about regular false positives though?

Short-term: create the PR manually.
Medium-term: We should fix brew bump-formula-pr in those cases to improve detection.

(Note, the detection could also match both the formula name and the version, which doesn't seems to be the case currently?)

This seems like a good idea 👍🏻

mharwani added a commit to runfinch/finch that referenced this pull request Feb 22, 2024
#828)

… PR bump

Issue #, if available:

*Description of changes:*
The latest release of Homebrew does not allow forcing multiple PRs
(Homebrew/brew#16664). This causes the
`release-homebrew` workflow to fail as it uses the `--force` option in
`bump-cask-pr` command which is disabled as of brew version 4.2.9. This
PR removes the `--force` flag to fix the workflow step.

Recent Homebrew workflow failure:
https://github.com/runfinch/finch/actions/runs/7997204281/job/21841199683

*Testing done:*



- [X] I've reviewed the guidance in CONTRIBUTING.md


#### License Acceptance

By submitting this pull request, I confirm that my contribution is made
under the terms of the Apache 2.0 license.

Signed-off-by: Mrudul Harwani <[email protected]>
@github-actions github-actions bot added the outdated PR was locked due to age label Mar 21, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 21, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
outdated PR was locked due to age
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants