mne-tools / mne-tools/mne-python
commits from GHA bots don't trigger CircleCI jobs
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 3.5k
- Forks
- 1.6k
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 100
Description
Noticed this most recently over at https://github.com/mne-tools/mne-python/pull/13558/commits/dc1c44fec4b2d7c7c1082c6e35b2c9619c085d9c
Since a GitHub Actions bot (specifically our Pre-commit bot) doesn't have a CircleCI account (as expected), the CircleCI jobs will fail when the bot makes a commit.
It's not the end of the world and usually I'll just manually push an empty commit to re-trigger the CI's, but in some cases I have found this to be annoying (for example in #13558 I'm trying to help a new contributor work through the PR).
I wonder if there is some work around we can implement to do give the bot the necessary context to trigger the CircleCI jobs.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the GitHub Actions and CircleCI configuration involved in the bot commit shown in PR #13558. Reproduce the behavior with a bot-authored commit and determine what context CircleCI requires. Done means those commits trigger the expected CircleCI jobs without manually pushing an empty commit.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100