Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/_sidebar_diataxis.json
Original file line number Diff line number Diff line change
Expand Up @@ -90,9 +90,9 @@
"href": "/docs/maintainer/knowledge_base/#apple-silicon-builds"
},
{
"type": "link",
"type": "doc",
"label": "Talk to the bots",
"href": "/docs/maintainer/conda_forge_yml/"
"id": "how-to/advanced/talk-to-the-bots"
},
{
"type": "link",
Expand Down
16 changes: 16 additions & 0 deletions docs/how-to/advanced/talk-to-the-bots.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
---
tags: [how-to, advanced]
---

# How to talk to the bots

Some parts of the conda-forge automation are exposed as "bot commands" that can be invoked from issue titles and comments. You can check the full list in the [admin-web-services](/docs/maintainer/infrastructure.md#admin-web-services) documentation.

Bot commands typically start with `@conda-forge-admin, please`. Bot commands can have two types of scope:

- Repository scope: The command is typed as the title of a new issue in the target feedstock, or in an issue comment.
- Pull request scope: The command is typed as a pull request comment or review.

Some commands may have dual behavior. For example `@conda-forge-admin, please rerender` can be used as an issue title to create a new PR after rerendering from `main`, but it can also be used within a PR to rerender the head branch and push a new commit automatically.

The bots will usually react to the comment with a 🚀 emoji, and later post a comment informing about progress and outcome.
Loading