Create a dedicated releases/changes logs section
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- JavaScript
- Stars
- 18
- Forks
- 66
- PR merge metrics
- No merged PRs in 30d
Description
Currently, we are publishing the release notes on Discord, Telegram and Github (sometimes) only.
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
Review the documentation structure and how release notes are currently represented; the issue names no file or entry point. Determine where a dedicated releases/changes section should live and how the Discord, Telegram, and GitHub notes should be organized. Done means the section exists and provides a clear home for release updates.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100