From 8e3c306a4f000e911c634338b1428c22fa6c4040 Mon Sep 17 00:00:00 2001 From: shollyman Date: Wed, 4 Nov 2020 12:00:04 -0800 Subject: [PATCH] docs: remove redundant step in submodule RELEASING.md guidance (#3141) The cited `go generate` is responsible for updating the repo reference in internal/version.go, so listing it both explicitly as a manual edit and a generate command seems redundant. --- RELEASING.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/RELEASING.md b/RELEASING.md index ace2c003f26..12e0c6104b9 100644 --- a/RELEASING.md +++ b/RELEASING.md @@ -131,8 +131,6 @@ To release a submodule: 1. On master, run `git log $CV.. -- datastore/` to list all the changes to the submodule directory since the last release. 1. Edit `datastore/CHANGES.md` to include a summary of the changes. -1. In `internal/version/version.go`, update `const Repo` to today's date with - the format `YYYYMMDD`. 1. In `internal/version` run `go generate`. 1. Commit the changes, ignoring the generated `.go-r` file. Push to your fork, and create a PR titled `chore(datastore): release $NV`.