-
Notifications
You must be signed in to change notification settings - Fork 180
Enable merge queue trigger for PR workflow #2063
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
base: main
Are you sure you want to change the base?
Conversation
…is for merge queues.
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.
Pull request overview
This PR enables GitHub merge queue support for AL-Go's Pull Request Handler workflow by adding the merge_group trigger and implementing necessary compatibility changes for how refs are handled during merge queue builds.
Key Changes:
- Addition of
merge_grouptrigger to Pull Request Handler workflow in both template variants - Implementation of conditional ref handling logic to support both standard PRs and merge queue events
- Documentation of breaking change in RELEASENOTES.md warning users about potential impacts
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Pull request overview
Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| > [!WARNING] | ||
| > If you rely on a custom workflow for merge queue validation, you may need to adjust your setup to avoid duplicate builds. | ||
| ## AL-Go Telemetry updates |
Copilot
AI
Jan 21, 2026
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.
The heading level was changed from ### to ##, which breaks the document hierarchy. This section should remain at the ### level to be consistent with other feature sections like "Merge queue support" and "Set default values for workflow inputs". The ## level appears to be reserved for major release version headings like "v8.1".
| ## AL-Go Telemetry updates | |
| ### AL-Go Telemetry updates |
❔What, Why & How
This adds the merge queue trigger to the PR workflow, and makes a few modifications to make it compatible with merge queue builds. This is mainly needed as the way refs are handled are a bit different in merge queues compared to regular PRs. The changes should not have any affect on regular PRs, only add compatibility with merge queues.
Related to issue: #
✅ Checklist