Closed adu-web3 closed 3 months ago
The recent updates enhance the GitHub Actions workflows by adding a new event trigger, merge_group
, to three files: forge-ci.yml
, lint.yml
, and slither.yml
. This addition allows the continuous integration (CI) process to respond to merge group events, improving responsiveness and flexibility in handling repository activities, while maintaining the existing functionality for pull requests and pushes.
Files | Change Summary |
---|---|
.github/workflows/forge-ci.yml, .github/workflows/lint.yml, .github/workflows/slither.yml | Added merge_group event trigger to improve CI responsiveness and expand conditions for workflow execution. |
🐇 In the land of code where bunnies hop,
New triggers sprout, never let them stop!
Merge groups now dance in CI's bright light,
Making workflows nimble, oh what a delight!
With every new change, we cheer and we play,
Hopping through code on this fine, sunny day! 🌼
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
Description
As described in comment https://github.com/ExocoreNetwork/exocore-contracts/pull/66#discussion_r1696535071, the checks would not be re-run when another pull request gets merged before merging a pull request. To enable checks being automatically re-run even if no new commit is pushed, we have set the main branch protection rules to require merge queue, and this pull request add
merge_group
to workflow files to trigger these checks for merge queueSummary by CodeRabbit
merge_group
, to the CI workflows, enhancing responsiveness to specific repository activities.merge_group
event.These changes provide more granular control over when CI processes run, potentially improving workflow efficiency and issue detection.