Skip to content

Commit e01bf3f

Browse files
authored
Merge pull request #600 from bwitt/merge-release-pr
Explicitly mention merging the release PR in the releasing a module version flow
2 parents 4f745d8 + 2058f04 commit e01bf3f

1 file changed

Lines changed: 5 additions & 4 deletions

File tree

_docs/releasing_version.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ last_modified_at: 2025-06-10
99
Creating a release is a three step process:
1010

1111
1. Create a release PR
12-
2. Review it
12+
2. Review and merge the release PR
1313
3. Do the actual release
1414

1515
## Before Preparing a release
@@ -18,7 +18,7 @@ Run [modulesync](https://voxpupuli.org/docs/updating-files-managed-with-modulesy
1818

1919
## Standard Release
2020

21-
### Create Release PR
21+
### Create a Release PR
2222

2323
To automatically create a "release PR", you need to be a member of the `voxpupuli` GitHub organization.
2424
Then you can browse to a module -> Actions -> `Prepare Release`.
@@ -32,7 +32,7 @@ It will automatically:
3232
* A pull request will be created
3333
* GitHub attaches the `skip-changelog` label
3434

35-
### Review the Release PR
35+
### Review and Merge the Release PR
3636

3737
This will have generated updates to the CHANGELOG.md, review each PR in the CHANGELOG to make sure they're labeled properly so that the CHANGELOG is correct:
3838

@@ -54,9 +54,10 @@ All commentary should be reviewed, but specifically looking for concensus around
5454
* Are there discussions about the tagging of any of the changes in the CHANGELOG.md?
5555
* Have you missed something needed for release?
5656

57+
Merge the PR when ready.
5758
The person who does the merge of the PR is expected to do the release below.
5859

59-
### Do the Release
60+
### Do the Actual Release
6061

6162
*Please note that in order to execute this rake task you must be in the __Collaborators__ group on GitHub for the module in question.*
6263

0 commit comments

Comments
 (0)