Skip to content

.github/workflows/check-prs.yml: allow use of brew bump#445

Merged
p-linnane merged 2 commits into
mainfrom
handle-brewbump
Jun 22, 2026
Merged

.github/workflows/check-prs.yml: allow use of brew bump#445
p-linnane merged 2 commits into
mainfrom
handle-brewbump

Conversation

@bevanjkay

Copy link
Copy Markdown
Member

Allow the use of brew bump and brew bump-(cask|formula)-pr in homebrew-cask and homebrew-core.

The early exit is included in the check-prs workflow because it allows scoping this to the appropriate repositories, if we don't care about this, can update the PR to include it in the check script instead.

Copilot AI review requested due to automatic review settings June 22, 2026 02:15

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates the .github “check-prs” workflow to treat certain Homebrew/homebrew-core and Homebrew/homebrew-cask pull requests as having a “complete template” when they were opened via brew bump, allowing a condensed PR body to pass the workflow’s template check.

Changes:

  • Add an early-exit in the “Check pull request template” step that marks the template as complete when the PR body contains a Created by \brew bump…`` marker for homebrew-core and homebrew-cask.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .github/workflows/check-prs.yml
Comment thread .github/workflows/check-prs.yml Outdated
Co-authored-by: Patrick Linnane <patrick@linnane.io>
@bevanjkay bevanjkay requested a review from p-linnane June 22, 2026 02:45
@p-linnane p-linnane merged commit a2561cd into main Jun 22, 2026
2 checks passed
@p-linnane p-linnane deleted the handle-brewbump branch June 22, 2026 02:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants