Inconsistent naming convention of taskfile commands
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 141
- Forks
- 146
- Avg merge
- 11h 7m
- Merged PRs (30d)
- 407
Description
The taskfile commands (executed usinggo-task in packages monorepo) have inconsistent naming convention. I think this is caused by creating all commands ad-hoc. It makes it hard to remember all the commands we have. We should have a convention for naming the commands going forward. I propose something like (action) (place) (misc) format. I will expand this further later.
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 taskfile commands used in the packages monorepo and inventory their current names. The issue proposes an action/place/misc convention but does not identify files, tests, or a finalized naming scheme. Done would require an agreed convention and consistent command names across the taskfiles.
Written by the indexing model from the issue text.
Assessment
- Domain
- build-system
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100