Include a CHANGELOG and include in release process

Open
#95 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
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
rust
Domain
documentation, release

Research direction

Start by reviewing the repository's current release process and determine where a CHANGELOG should live. Done means the changelog exists and its maintenance is included in the release process; the issue provides no file or test entry points.

Written by the indexing model from the issue text.

Description

This issue has no description.

Dominant language
Rust
Stars
0
Forks
2
Avg merge
5d 4h
Merged PRs (30d)
2

Contributor guide

No contributing guide indexed for this repository

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 DiamondLightSource/glazed

All issues in DiamondLightSource/glazed

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.