Turn discussions into issues, close discussions
Open
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 1.6k
- Forks
- 211
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 6
Description
Discussions are not well integrated into GitHub.
- cross referencing not functional
- updates not showing under heads-changes channel.
- goes unnoticed as opposed to issues.
- double the work, no return on effort: not Paretto
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
The issue does not identify a repository file, test, or entry point. First clarify whether the desired change is a GitHub workflow or a repository feature, define how discussions should become issues, and establish acceptance criteria for cross-references, heads-changes updates, and closing discussions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100