diff options
| author | bors[bot] <26634292+bors[bot]@users.noreply.github.com> | 2021-02-12 18:20:27 +0000 |
|---|---|---|
| committer | GitHub <[email protected]> | 2021-02-12 18:20:27 +0000 |
| commit | 935830d05bcf5f0c648e636dcbc8848a201467c0 (patch) | |
| tree | ff289b26eb96e2dd9fdfaf24f5c73f0f2487a2d1 /docs/dev | |
| parent | 88253907f4bc3beaa7b8f2e58cb652f653f92d56 (diff) | |
| parent | 8814d1368d6712fd85074d77e33be610f01566c4 (diff) | |
Merge #7655
7655: Include a commit log summary in the changelog r=matklad a=lnicola
This version omits any direct pushes, and maybe even pull requests merged from the GitHub UI. But I think it makes writing the release notes easier.
Co-authored-by: Laurențiu Nicola <[email protected]>
Diffstat (limited to 'docs/dev')
| -rw-r--r-- | docs/dev/README.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/docs/dev/README.md b/docs/dev/README.md index 9b9b18102..d6fae5295 100644 --- a/docs/dev/README.md +++ b/docs/dev/README.md | |||
| @@ -218,8 +218,7 @@ Release steps: | |||
| 218 | * makes a GitHub release | 218 | * makes a GitHub release |
| 219 | * pushes VS Code extension to the marketplace | 219 | * pushes VS Code extension to the marketplace |
| 220 | * create new changelog in `rust-analyzer.github.io` | 220 | * create new changelog in `rust-analyzer.github.io` |
| 221 | * create `rust-analyzer.github.io/git.log` file with the log of merge commits since last release | 221 | 2. While the release is in progress, fill in the changelog |
| 222 | 2. While the release is in progress, fill-in the changelog using `git.log` | ||
| 223 | 3. Commit & push the changelog | 222 | 3. Commit & push the changelog |
| 224 | 4. Tweet | 223 | 4. Tweet |
| 225 | 5. Inside `rust-analyzer`, run `cargo xtask promote` -- this will create a PR to rust-lang/rust updating rust-analyzer's submodule. | 224 | 5. Inside `rust-analyzer`, run `cargo xtask promote` -- this will create a PR to rust-lang/rust updating rust-analyzer's submodule. |