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.

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

ci: Prevent CI workflows on bot commits and README updates #455

Closed
wants to merge 2 commits into from

Conversation

justinpolygon
Copy link
Contributor

This commit addresses an issue where the automated commits made by the code coverage bot, specifically updates to README.md, trigger the lint and test GitHub Actions workflows to stop. This behaviour leads to race conditions and unnecessary CI runs on commits that don't affect the codebase. A good example here this PR #453 where the badge gets updated and stops the tests from completing. It is also blocking this PR #454.

Changes implemented:

  • Added [skip ci] to the commit message in the code-coverage workflow to prevent triggering CI workflows on bot-generated commits.
  • Modified lint.yaml, codeql.yml, and test.yaml workflows to Included paths-ignore for README.md, so changes to this file alone won't trigger the workflows.

By combining these methods, we can stop that pesky CI workflow and only run when relevant code changes occur.

@justinpolygon
Copy link
Contributor Author

justinpolygon commented Oct 11, 2024

As a prime example, it has even stopped this PR. You might wonder, why are we only seeing this now? Well, we have seen it in the past, it's just that code coverage badge used to take a while so we'd normally pass the tests before it did anything. I guess they must have sped up the coverage run, or our tests are taking longer, and now we're seeing it all the time.

@justinpolygon justinpolygon deleted the jw-fix-ci-badge branch October 11, 2024 14:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants