CI: Update CircleCI or move to Github Actions for CI process
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
Research direction
Start by inspecting the current CircleCI configuration and the local CI tests referenced in the issue. Determine whether updating CircleCI or moving to GitHub Actions is appropriate; done means the selected CI process runs the local tests reliably without the current false positives.
Written by the indexing model from the issue text.
Description
The current CircleCI is very much out of date and triggering false positives. We should either migrate things to the new CircleCI configuration or switch to using GithubActions to perform the local CI tests.
- Dominant language
- Rust
- Stars
- 29
- Forks
- 14
- Avg merge
- 3h 15m
- Merged PRs (30d)
- 2
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.
More from mozilla/rust-ece
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Security review Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
All issues in mozilla/rust-ece
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
VirusTotal/yara-x#777 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
stratum-mining/stratum#2404 ·
-
bug ci good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 88/100