TooAngel / TooAngel/worlddriven
Handling of github Issues
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 18
- Forks
- 15
- Avg merge
- 8d 14h
- Merged PRs (30d)
- 5
Description
The idea of world driven is to remove the owner of a (github) repository, this works out good in regards to Pull Requests and also due to the github issue feature on closing issues, too.
But how to handle new issues? Creating is easy. How about assigning and labels?
First ideas which come to my mind:
As soon as a PR is opened which related to an issue, the contributor is assigned with that issue.
For labels, I don't have a very good idea yet. Best idea so far: Have some kind of keywords: label: bug/unlabel: bug which someone can write and you can vote via 👍 and 👎. Similar to PR merge (maybe faster) the tag is added.
WDYT?
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
No files, tests, or entry points are named; begin by reading the issue discussion and its proposed GitHub issue workflows. The work is not ready until behavior for assigning contributors and handling label proposals and votes is decided clearly enough to implement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100