Skip to content

ci(Mergify): configuration update#4104

Open
Aire-One wants to merge 2 commits into
masterfrom
mergify/Aire-One/Id1942c3ddfb2ff007edf6c13a8528651e1aaf6eb
Open

ci(Mergify): configuration update#4104
Aire-One wants to merge 2 commits into
masterfrom
mergify/Aire-One/Id1942c3ddfb2ff007edf6c13a8528651e1aaf6eb

Conversation

@Aire-One

Copy link
Copy Markdown
Member

This change has been made by @Aire-One from the Mergify config editor.

Signed-off-by: Aire-One <null>
@Aire-One

Copy link
Copy Markdown
Member Author

Close: #4045

@awesome-robot

Copy link
Copy Markdown

Documentation has been updated for this PR.

Compare view: awesomeWM/apidoc@bd086ed...2bf1a68
Relevant changes: awesomeWM/apidoc@c0aa6bc
Comparison against master (gh-pages): awesomeWM/apidoc@gh-pages...2bf1a68

@codecov

codecov Bot commented May 19, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.42%. Comparing base (c104846) to head (8ffad56).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #4104      +/-   ##
==========================================
- Coverage   90.42%   90.42%   -0.01%     
==========================================
  Files         940      940              
  Lines       60290    60290              
  Branches     1139     1139              
==========================================
- Hits        54516    54515       -1     
- Misses       5268     5269       +1     
  Partials      506      506              

see 2 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@Aire-One

Copy link
Copy Markdown
Member Author

@actionless, I went with a label mergify/squash to make Mergify squash commits and default strategy is merge, like it was before. I have the hope we can have PRs with clean commits more often than the need to squash.

Also, I moved the dissmiss_reviews action to its own rule block, so it is more understandable and can work for real.

Note, for consistency and readability, I renamed the old no-mergify label to mergify/no-merge.

@Aire-One

Copy link
Copy Markdown
Member Author

Uhuh, nice 😹

@Aire-One Aire-One added the mergify/squash Use the Mergify squash method for automatic merge label May 19, 2026
@awesome-robot

Copy link
Copy Markdown

Documentation has been updated for this PR.

Compare view: awesomeWM/apidoc@bd086ed...6670856
Relevant changes: awesomeWM/apidoc@bc8c289
Comparison against master (gh-pages): awesomeWM/apidoc@gh-pages...6670856

@actionless

Copy link
Copy Markdown
Member

I have the hope we can have PRs with clean commits more often than the need to squash.

hope is counter-productive when estimating quantifiable properties - we could simply take 20+ latest or random PRs and see if it's the case or not

mergify Bot pushed a commit to Mergifyio/docs that referenced this pull request May 20, 2026
The example in doc is not a valid YAML syntax.

Discovered while working on awesomeWM/awesome#4104
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

mergify/squash Use the Mergify squash method for automatic merge

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants