-
-
Notifications
You must be signed in to change notification settings - Fork 151
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
Make only-new-issues work with Merge Queues, not just Pull Requests #956
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Our org is running into a similar issue as well. I probably missed something that don't understand about merge groups but this is what I changed. It seems to work but not sure if thats exactly what's needed to support merge groups. |
@strantalis Did/can you createa PR with those changes, to hopefully get a full review? |
@flimzy I don't have a pr open. I will open one to hopefully get a conversation started. |
EDIT: I found how to trigger the event. |
Currently, The addition of The support of Currently, as a workaround to use
name: golangci-lint
on:
pull_request:
merge_group:
jobs:
golangci-lint:
name: lint
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- uses: actions/setup-go@v5
with:
go-version: stable
- name: golangci-lint (PR)
if: ${{ github.event_name == 'pull_request' }}
uses: golangci/golangci-lint-action@v5
with:
version: v1.57
only-new-issues: true
- name: golangci-lint (queue)
if: ${{ github.event_name == 'merge_group' }}
uses: golangci/golangci-lint-action@v5
with:
version: v1.57
args: --new-from-rev=${{ github.event.merge_group.base_sha }} |
FYI, since v5.1.0, the events Note: for ExamplesFor pull requests: name: golangci-lint
on:
pull_request:
jobs:
golangci-lint:
name: lint
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version: stable
- name: golangci-lint
uses: golangci/golangci-lint-action@v5
with:
version: v1.57
only-new-issues: true For push: name: golangci-lint
on:
push:
jobs:
golangci-lint:
name: lint
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version: stable
- name: golangci-lint
uses: golangci/golangci-lint-action@v5
with:
version: v1.57
only-new-issues: true For pull requests, and push: name: golangci-lint
on:
push:
pull_request:
jobs:
golangci-lint:
name: lint
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version: stable
- name: golangci-lint
uses: golangci/golangci-lint-action@v5
with:
version: v1.57
only-new-issues: true For pull requests and merge queues: name: golangci-lint
on:
pull_request:
merge_group:
jobs:
golangci-lint:
name: lint
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- uses: actions/setup-go@v5
with:
go-version: stable
- name: golangci-lint
uses: golangci/golangci-lint-action@v5
with:
version: v1.57
only-new-issues: true For pull requests, merge queues, and push: name: golangci-lint
on:
push:
pull_request:
merge_group:
jobs:
golangci-lint:
name: lint
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
with:
fetch-depth: 0
- uses: actions/setup-go@v5
with:
go-version: stable
- name: golangci-lint
uses: golangci/golangci-lint-action@v5
with:
version: v1.57
only-new-issues: true |
@ldez Workflows seem to be working. Just wanted to say thanks for the help. |
Welcome
Your feature request related to a problem? Please describe.
only-new-issues
is fantastic, but it currently only works when the GitHub event_name ispull_request
. Please add support for themerge_group
event name, so that this feature can work with merge queues as well.Merge queues are a powerful feature of GitHub for teams that merge many pull requests per day. It lets you queue up multiple pull requests to be merged in a row. Adding a PR to the queue triggers a new run of the status checks, and once the required status checks pass, that PR is merged.
Describe the solution you'd like.
We just need
only-new-issues
to apply when the GitHub event ismerge_group
. Insrc/run.ts
we would change this:to this:
(I'm assuming there would need to be some additional changes to figure out the patch, but nothing too bad)
Describe alternatives you've considered.
My main alternatives are
Additional context.
No response
The text was updated successfully, but these errors were encountered: