> For the complete documentation index, see [llms.txt](https://wiki.solids.group/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.solids.group/alamo/github-integration-with-slack.md).

# GitHub Integration with Slack

After adding the GitHub app to Slack, configure different channels within the Slack workspace to show GitHub notifications as desired.

When you subscribe to notifications on a given Slack channel, the notifications may only be shown to you, not to the other members of the channel. More details are available in the [GitHub Slack integration configuration documentation](https://github.com/integrations/slack#configuration).

Enter these commands in the following channels to get the appropriate notifications:

| Slack channel  | Command                                         |
| -------------- | ----------------------------------------------- |
| `alamo-commit` | `/github subscribe solidsgroup/alamo commits:*` |
| `alamo-issues` | `/github subscribe solidsgroup/alamo issues`    |

To subscribe to other notifications, either add them to the existing channels or add them directly to the GitHub channel that appears when you add the app.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.solids.group/alamo/github-integration-with-slack.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.