Skip to content

Commit 94f9358

Browse files
committed
Add please ping conda-forge/core
1 parent 0c602c3 commit 94f9358

File tree

1 file changed

+15
-8
lines changed

1 file changed

+15
-8
lines changed

src/maintainer/infrastructure.rst

Lines changed: 15 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -128,6 +128,13 @@ Entering this command in the PR of a feedstock or staged-recipes will have the a
128128
associated with the repo. This command can be useful for people who are not yet members of conda-forge and
129129
so cannot @-mention the ``staged-recipes`` team for PR reviews.
130130

131+
@conda-forge-admin, please ping conda-forge/core
132+
------------------------------------
133+
134+
Entering this command in the PR of a feedstock or staged-recipes will have the admin bot @-mention `conda-forge/core <https://conda-forge.org/docs/orga/governance.html#teams-roles>`_.
135+
This command can be useful for people who are not yet members of conda-forge and
136+
so cannot @-mention someone due to the general GitHub limitations.
137+
131138
@conda-forge-admin, please rerun bot
132139
------------------------------------
133140

@@ -291,23 +298,23 @@ GitHub Actions.
291298
Automerge
292299
.........
293300

294-
The automerge service uses the GitHub action in this `repo <https://github.com/conda-forge/automerge-action>`_. This action runs out of a
295-
Docker `container <https://hub.docker.com/repository/docker/condaforge/automerge-action>`_ on the ``prod`` tag. See the
296-
repo `README.md <https://github.com/conda-forge/automerge-action#readme>`_ for more details. PRs are automatically merged if they satisfy either
301+
The automerge service uses the GitHub action in this `repo <https://github.com/conda-forge/automerge-action>`_. This action runs out of a
302+
Docker `container <https://hub.docker.com/repository/docker/condaforge/automerge-action>`_ on the ``prod`` tag. See the
303+
repo `README.md <https://github.com/conda-forge/automerge-action#readme>`_ for more details. PRs are automatically merged if they satisfy either
297304
of the two following sets of conditions:
298305

299306
1. are from the ``regro-cf-autotick-bot``, have ``[bot-automerge]`` in the title, all statuses are passing, and the feedstock allows automerge
300-
2. have the ``automerge`` label and all statuses are passing.
307+
2. have the ``automerge`` label and all statuses are passing.
301308

302-
For PRs from the ``regro-cf-autotick-bot``, it can be useful to remove the ``[bot-automerge]`` slug from the PR title if you are making
309+
For PRs from the ``regro-cf-autotick-bot``, it can be useful to remove the ``[bot-automerge]`` slug from the PR title if you are making
303310
edits to the PR.
304311

305312
Rerendering
306313
...........
307314

308-
The rerendering service is triggered by the Heroku app. It uses the GitHub action in this `repo <https://github.com/conda-forge/webservices-dispatch-action>`_.
309-
This action runs out of a Docker `container <https://hub.docker.com/repository/docker/condaforge/webservices-dispatch-action>`_ on the ``prod`` tag. See the
310-
repo `README.md <https://github.com/conda-forge/webservices-dispatch-action#readme>`_ for more details.
315+
The rerendering service is triggered by the Heroku app. It uses the GitHub action in this `repo <https://github.com/conda-forge/webservices-dispatch-action>`_.
316+
This action runs out of a Docker `container <https://hub.docker.com/repository/docker/condaforge/webservices-dispatch-action>`_ on the ``prod`` tag. See the
317+
repo `README.md <https://github.com/conda-forge/webservices-dispatch-action#readme>`_ for more details.
311318

312319

313320
Skipping CI builds

0 commit comments

Comments
 (0)