Chainsmoker future improvements
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 379
- Avg merge
- 2h 8m
- Merged PRs (30d)
- 6
Description
Hiya @orta 👋
Thought I'd touch base about how to move forward with maintaining chainsmoker. I've gotten my repo updated and the tooling switched over and configured to match the Danger repo. The code is exactly the same as what's here (save the relative import in the test file). Released as 1.0.0. 🚀
The question I have is how to handle bug reports (which hopefully will be few) and improvement suggestions.
One option would be to leave comments in the copy here asking folks to open issues/PRs on my repo, and I add you as a maintainer.
Thoughts?
My repo is here: https://github.com/paulmelnikow/chainsmoker
Contributor guide
Research direction
Start with the issue body and the linked chainsmoker repository, since no files or tests are named. Determine whether bug reports and improvement suggestions should remain here or move to that repository; done means the maintenance location and responsibilities are clearly agreed and recorded.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100