✨ CHANGELOG
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 23h 54m
- Merged PRs (30d)
- 29
Description
Would you like to include a changelog?
A changelog contains a curated, chronologically ordered list of notable changes for each project version. To make it easier for users and contributors to see precisely what notable changes have been made between each project release (or version). Whether consumers or developers, the end users of software are human beings, who care about what's in the software. When the software changes, people want to know why and how.
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 reading the linked keepachangelog.com guidance, then inspect the OpenINF repository's existing community health files and organization-level metadata. Determine which projects and releases the changelog should cover, and define the expected location and update process before considering the work complete.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100