GitHub issues over time plot
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Need to migrate the GitHub issue data to motherduck
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
No files, tests, or entry points are named. Start by locating the code that collects GitHub issue data and produces the issues-over-time plot, then determine how the data is currently stored before planning its migration to MotherDuck; done means the plot still works from the migrated data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, python
- Domain
- data-visualization, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100