Skip to content

Commit ce88fd2

Browse files
authored
Update updating_pkgs.md - maintainer expectations for bot PRs
Adding more description of what a maintainer should expect for automatic bot PRs.
1 parent 6a344b9 commit ce88fd2

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/maintainer/updating_pkgs.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,9 +47,9 @@ For these reasons, maintainers are asked to fork the feedstock to their personal
4747

4848
<a id="pushing-to-regro-cf-autotick-bot-branch"></a>
4949

50-
#### Pushing to regro-cf-autotick-bot branch
50+
#### Pushing/Pulling to regro-cf-autotick-bot branch
5151

52-
When a new version of a package is released on PyPI/CRAN/.., we have a bot that automatically creates version updates for the feedstock. In most cases you can simply merge this PR and it should include all changes. When certain things have changed upstream, e.g. the dependencies, you will still have to do changes to the created PR. As feedstock maintainer, you don't have to create a new PR for that but can simply push to the branch the bot created. There are two alternatives to push to the branch of the bot:
52+
When a new version of a package is released on PyPI/CRAN/.., we have a bot that automatically creates version updates for the feedstock. In most cases you can simply merge this PR and it should include all changes. When certain things have changed upstream, e.g. the dependencies, you will still have to do changes to the created PR. As feedstock maintainer, you don't have to create a new PR for that but can simply push to the branch the bot created. These bots are checking tens of thousands of packages, so it may be more than a few hours before the bot detects a change and makes an automatic pull request. One procedure is to wait for up to 24 hours to see if you receive an email with the automatic pull request, which may occur at https://github.com/conda-forge/package-you-maintain with a subject line like package-you-maintain Version X.Z. With default github settings, you will get an email notificaiton. You can follow the checklist on the pull request and then click to merge. There are two alternatives to push to the branch of the bot:
5353

5454
1. Manually setting up git remotes:
5555

0 commit comments

Comments
 (0)