Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Release instructions
develop
, cut a release branch namedrelease/X.Y.Z
for your changes.safe-redirect-manager.php
,package-lock.json
,package.json
, andreadme.txt
if it does not already reflect the version being released. Insafe-redirect-manager.php
update both the plugin "Version:" property and the pluginSRM_VERSION
constant.readme.txt
andCHANGELOG.md
.CREDITS.md
file with any new contributors, confirm maintainers are accurate.README.md
is geared toward GitHub andreadme.txt
contains WordPress.org-specific content. The two are slightly different..gitattributes
.develop
(or merge the pull request), then do the same fordevelop
intotrunk
, ensuring you pull the most recent changes intodevelop
first (git checkout develop && git pull origin develop && git checkout trunk && git merge --no-ff develop
).trunk
contains the stable development version.trunk
branch to GitHub (e.g.git push origin trunk
).trunk
todevelop
to ensure no additional changes were missed.trunk
branch. Paste the changelog fromCHANGELOG.md
into the body of the release and include a link to the closed issues on the milestone (e.g.https://github.com/10up/safe-redirect-manager/milestone/#?closed=1
).Due date (optional)
field) and link to GitHub release (in theDescription
field), then close the milestone.X.Y.Z
do not make it into the release, update their milestone toX.Y.Z+1
,X.Y+1.0
,X+1.0.0
orFuture Release
.