practicalli / practicalli/clojure-web-services
GitHub analytics project
Open
Nobody has claimed this yet.
project
- Dominant language
- Markdown
- Stars
- 16
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
A website that tracks specific GitHub / GitLab projects and creates analytics for a project
- number of issues (raised, closed, marked stale) / PR's (raised, merged, closed) / commits / forks / stars / unstars / etc over time - daily, weekly, monthly, yearly
Constraints
Should have minimal impact on GitHub repositories analysed
No files or settings required for public repos
Export data
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 names no files, tests, or entry points. Start by scoping the proposed website and its GitHub/GitLab data sources, then define how time-based analytics and data export should work. Done would require meeting the stated low-impact and public-repository constraints without repository files or settings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, gitlab
- Domain
- analytics, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100