Investigate using GitHub contribution actions for generating stats
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Investigate using the automated action for generation contribution stats on repos from github: https://github.blog/2023-10-23-how-to-gain-insight-into-your-project-contributors/
Additional context
https://nfcore.slack.com/archives/C02D7SW8LR3/p1698216565618619
@ewels told me to
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 reading the linked GitHub blog post and the referenced Slack discussion to understand the proposed contribution-statistics action. Investigate whether it fits the stats project's intended output and document the findings, including a clear recommendation or next step. No repository files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- analytics, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100