nodejs / nodejs/package-maintenance
Suggestion: Tooling to assist maintenance errands
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 423
- Forks
- 147
- PR merge metrics
- No merged PRs in 30d
Description
Travis CI recently informed me that I have over 800 packages using it.
I've done up the following tooling to assist in automating the maintenance of my packages as much as possible, they have been used for years, and probably others will find them useful:
- https://github.com/bevry/badges - generate readme badges
- https://github.com/bevry/projectz - automate readmes
- https://github.com/bevry/awesome-travis - travisci scripts for testing, publishing, deployment, etc
- https://github.com/bevry/boundation - scaffold projects with the above
If you have your own, post them too.
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
Start by reviewing the four linked repositories: badges, projectz, awesome-travis, and boundation, along with the discussion in this issue. The issue does not define a specific change or acceptance criteria, so clarify whether the goal is to document these tools, integrate them, or collect additional maintenance tooling before starting.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100