actions / actions/starter-workflows
Number Tracker
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.1k
- Forks
- 7.3k
- PR merge metrics
- No merged PRs in 30d
Description
Create and maintain a tracker to monitor specific numbers or progress related to the repository. This could be used for tracking issue numbers, pull request numbers, deployment counts, or any other metrics as needed for the project. The tracker should be easy to update and reference by team members.
Proposed tasks:
- Define what numbers or metrics should be tracked (e.g., issue count, pull request count).
- Create a structured format (e.g., table or checklist) within the issue for easy updating.
- Regularly update the tracker as new numbers become relevant.
- Designate responsible team member(s) for maintaining the tracker.
Feel free to comment with suggestions for numbers to track or improvements to the tracking process.
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
No files, tests, or entry points are named. First define the metrics to track and agree on the responsible team members, then create a structured issue table or checklist; it is done when the selected numbers are documented, easy to update, and assigned for maintenance.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100