research-software-ecosystem / research-software-ecosystem/content
Managing the curation maintenance burden (pull requests)
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 48
- Forks
- 35
- Avg merge
- 19m
- Merged PRs (30d)
- 887
Description
One of many issues around GitHub-based content management for bio.tools.
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-based content-management issue (#1) and the surrounding context for bio.tools. No files, tests, or implementation entry points are named, and the desired outcome for reducing pull-request curation burden is not defined; clarify the scope and completion criteria before choosing an implementation path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100