OpenTabletDriver / OpenTabletDriver/opentabletdriver.github.io
Auto label PR's
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 36
- Forks
- 10
- Avg merge
- 12h 32m
- Merged PRs (30d)
- 9
Description
There are some labels which in some cases can easily be applied based on files changed:
| Label | Path |
|---|---|
ci |
/.github/workflows/* |
documentation |
*.md in root except index or docs(?) folder |
linting |
need to compile a list, but linter.yml and some other config files |
meta |
**/*.sh, /.github/*, /.*, more? |
styling |
usually assets/ but with exceptions? |
wiki |
/_wiki/* |
Some consideration has to be done as to whether we should use the labels this well-defined, or if such strict label usage should be kept to a minimum, e.g. #65 technically has styling changes but it shouldn't actually affect styling.
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
Review the proposed paths under /.github/workflows, root Markdown files, linter.yml, shell files, assets/, and /_wiki/. Decide how strictly labels should follow changed files, including the exceptions described for documentation and styling. Done means the label rules and their exceptions are defined well enough to implement consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100