From d8a735405325ddffc7503bd90dee6be7f2e2742a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adri=C3=A1n=20Chaves?= Date: Fri, 24 Apr 2020 15:42:40 +0200 Subject: [PATCH] Updated Scrapy release procedure (markdown) --- Scrapy-release-procedure.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/Scrapy-release-procedure.md b/Scrapy-release-procedure.md index fccce6f..0921987 100644 --- a/Scrapy-release-procedure.md +++ b/Scrapy-release-procedure.md @@ -129,6 +129,10 @@ may take a while depending on the conda-forge build queue. Once builds are OK, the pull request is ready to merge and packages will be uploaded to the `conda-forge` channel automatically. +Alternatively, you can wait for https://github.com/regro-cf-autotick-bot to create +such a pull request, and just edit it as needed (you should be able to commit directly to +it, even though the GitHub online editor). + ## Cherry-pick into master If you’ve released a patch version, you should cherry-pick the required commits into master (exclude version-bumping changes).