Rethink CircleCI workflow triggers
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 21
- Forks
- 23
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 17
Description
CircleCI is set up to run a suite of tests on branches.
At the moment it looks like it runs the build_and_test workflow on any non main branch.
One problem with this is that when contributors raise a PR from a form, and their fork is on main and targeting main, our CI won't run. This means we have to merge without automated tests - which is very very bad.
Another problem I think is that any branch which is pushed will have CI run on it. But this is likely to be a waste of computation on 80% of branches.
I think the setup we want is to run CircleCI on any open PR, regardless of what the branch is. Maybe even non-draft PRs, if we can do that.
What that really means is that CI tests only run on branches which are complete (or close to complete)
Contributor guide
No contributing guide indexed for this repository
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 locating the CircleCI configuration and the build_and_test workflow mentioned in the issue. Check how branch pushes and pull requests currently trigger it, then update the triggers so open pull requests run the suite without unnecessary branch builds. Done means fork-based and main-to-main pull requests receive automated tests while unrelated branch pushes do not.
Written by the indexing model from the issue text.
Assessment
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100