From 84851914488b2f3f6388a0760ee04306e4c2fc18 Mon Sep 17 00:00:00 2001 From: Jelle Zijlstra Date: Wed, 1 Dec 2021 13:47:33 -0800 Subject: [PATCH] slightly better example link (#2617) Since we also need to update two places in the docs --- docs/contributing/release_process.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/contributing/release_process.md b/docs/contributing/release_process.md index 718ea3d..9ee7dbc 100644 --- a/docs/contributing/release_process.md +++ b/docs/contributing/release_process.md @@ -8,8 +8,8 @@ explain what everything does and how to release _Black_ using said automation. To cut a release, you must be a _Black_ maintainer with `GitHub Release` creation access. Using this access, the release process is: -1. Cut a new PR editing `CHANGES.md` to version the latest changes - 1. Example PR: https://github.com/psf/black/pull/2192 +1. Cut a new PR editing `CHANGES.md` and the docs to version the latest changes + 1. Example PR: [#2616](https://github.com/psf/black/pull/2616) 2. Example title: `Update CHANGES.md for XX.X release` 2. Once the release PR is merged ensure all CI passes 1. If not, ensure there is an Issue open for the cause of failing CI (generally we'd -- 2.39.2