Add Changelog to Guidelines

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

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
documentation

Research direction

No file or test is named. Start by reviewing the repository's guideline structure and any existing version-history conventions, then determine where a changelog belongs. Done means users who started in 2025 can identify what changed in 2026.

Written by the indexing model from the issue text.

Description

issue request

For example, should make it easy for people who started using guidelines in 2025 to see what is updated in 2026.

Dominant language
Rust
Stars
200
Forks
25
Avg merge
3m
Merged PRs (30d)
1

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 microsoft/rust-guidelines

All issues in microsoft/rust-guidelines

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.