nodejs / nodejs/node-core-utils
Don't require full CI when `.github/` is the only change (and others)
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 314
- Forks
- 137
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 24
Description
This might also require policy changes on nodejs/node, but for PRs changing Actions we don't need to run full CI. Same goes for PRs changing CODEOWNERS, or linter rules, among other files. I suggest we create a .jenkinsignore file or something on nodejs/node so we can store the rules there instead of here.
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
The issue mentions a proposed .jenkinsignore file and policy changes in nodejs/node. Start by reviewing how full CI decisions are currently defined and how nodejs/node handles Actions, CODEOWNERS, and linter-rule changes. Done means agreed rules can skip full CI for those changes and cover the other intended file categories.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100