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.

Sign up for GitHub

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

fix(mergify): Mergify config needs adjusting for latest mergify releases #6321

Merged
merged 5 commits into from
Jan 3, 2025
Merged

fix(mergify): Mergify config needs adjusting for latest mergify releases #6321

Changes from 1 commit
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
3551f79
fix(mergify): Mergify config needs adjusting for latest mergify releases
jasonmcintosh Dec 18, 2024
02f8f78
fix(mergify): Add integration test checks
jasonmcintosh Dec 18, 2024
68777f7
fix(mergify): Add integration test checks
jasonmcintosh Dec 18, 2024
f663657
fix(mergify): Add integration test checks
jasonmcintosh Dec 18, 2024
1c8018c
fix(mergify): Use just queue_conditions
jasonmcintosh Jan 3, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
fix(mergify): Add integration test checks
  • Loading branch information
@jasonmcintosh
jasonmcintosh committed Dec 18, 2024
commit 02f8f786410afe8dac14a7e6185cd6c0acf6299f
2 changes: 2 additions & 0 deletions .mergify.yml
View file
Original file line number Diff line number Diff line change
@@ -3,8 +3,10 @@ queue_rules:
merge_method: squash
queue_conditions:
Copy link
Contributor

Choose a reason for hiding this comment

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

From https://docs.mergify.com/configuration/file-format/#queue-rules it looks like we don't need to duplicate queue_conditions in merge_conditions. From https://docs.mergify.com/merge-queue/setup/#configuring-the-merge-queue-rules it looks like we only need one. I'd probably stick with queue_conditions and ditch merge_conditions.

Copy link
Member Author

Choose a reason for hiding this comment

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

Frankly not sure even need that since branch protection rules SHOULD cover these. IF we have branch rules set ;)

- check-success=build
- check-sucess=it-test
merge_conditions:
- check-success=build
- check-sucess=it-test

pull_request_rules:
- name: Make sure PR are up to date before merging
Loading