Add changelog

Open
#19 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
git
Domain
release

Research direction

Start by reviewing the suggested git-cliff tool and the repository's existing release-related files. Determine the intended changelog location and generation workflow; done means the project has a usable changelog setup consistent with the chosen approach.

Written by the indexing model from the issue text.

Description

Dominant language
Rust
Stars
112
Forks
2
Avg merge
2h 52m
Merged PRs (30d)
13

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from terror/present

All issues in terror/present

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.