tarantool / tarantool/graphqlapi
changelog: reformatting according to the common style
Open
Nobody has claimed this yet.
- Dominant language
- Lua
- Stars
- 2
- Forks
- 0
- Avg merge
- 4h 56m
- Merged PRs (30d)
- 4
Description
The format is based on Keep a Changelog
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
Locate the repository's changelog and compare its current format with the linked Keep a Changelog 1.1.0 guidance. Reformat the changelog to follow that common style, then review the result for consistent headings and entries.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100