Customizing notifications for GitHub in Teams - GitHub Docs Skip to main content GitHub Docs Version: Free, Pro, & Team Search or ask Copilot Search or ask Copilot Select language: current language is English Search or ask Copilot Search or ask Copilot Open menu Collapse sidebar Expand sidebar Scroll breadcrumbs left * Home * Integrations * How-tos * Teams * Customize notifications Scroll breadcrumbs right Integrations * * * Concepts * About integrations * Featured integrations * About building integrations * GitHub Developer Program * How-tos * Slack * Integrate GitHub with Slack * Use GitHub in Slack * Customize notifications * Teams * Integrate GitHub with Teams * Use GitHub in Teams * Customize notifications * Schedule reminders * Reference * Slack permissions * Teams permissions * Teams command reference * Tutorials * Slack * Create issues * Manage issues * Teams * Create issues * Manage issues and PRs Customizing notifications for GitHub in Teams Customize GitHub notifications to manage your work within Teams. Copy as Markdown In this article * Filtering notifications * GitHub Actions workflow notifications * Deployment notifications You can customize your notifications by subscribing to activity that is relevant to your Microsoft Teams channel, and unsubscribing from activity that is less helpful to your project. Notifications enabled by default The following notifications are enabled by default, but you can disable any of them using the @GitHub unsubscribe OWNER/REPO [FEATURE] command. Feature Description issues Opened, closed, or reopened issues. pulls New, merged, closed, or reopened pull requests. commits New commits on the default branch (usually main ). comments New comments on issues and pull requests. deployments Deployment status updates. releases New releases and pre-releases published. Note Repository notifications are also enabled by default. You will be notified when your repository is made public or deleted. This notification cannot be disabled, as repository updates are destructive activities. Notifications disabled by default The following notifications are disabled by default, but you can enable any of them using the @GitHub subscribe owner/repo [FEATURE] command. Feature Description reviews Pull request reviews. workflows GitHub Actions workflow runs and approval notifications. branches Branch creation and deletion. discussions Discussions created or answered. +label:"YOUR-LABEL" Filter issues, pull requests, and comments based on their labels. You can subscribe or unsubscribe from multiple settings at once. For example: * To turn on activity for pull request reviews and comments, use @GitHub subscribe OWNER/REPO reviews comments . * To turn off activity for issues and pull requests, use @GitHub unsubscribe OWNER/REPO issues pulls . Filtering notifications You can further customize your notifications with branch and label filters. Branch filters allow you to filter commit notifications based on branch names, while label filters allow you to filter issue and pull request notifications based on labels applied to them. Branch filters for commit notifications Branch filters allow you to filter commit notifications based on branch names. By default when you subscribe to the commits event, you will get notifications for your default branch. However, you can choose to filter on a specific branch, or a pattern of branches or all branches. Example configuration Description @GitHub subscribe OWNER/REPO commits Receive commit notifications for the default branch. @GitHub subscribe OWNER/REPO commits:main Only receive commit notifications for the main branch. @GitHub subscribe OWNER/REPO commits:feature/* Receive commit notifications for all branches that start with feature/ . @GitHub subscribe OWNER/REPO commits:* Receive commit notifications for all branches. You can unsubscribe from the commits feature using @GitHub unsubscribe OWNER/REPO commits . Note You may have previously used the commits:all filter to receive commit notifications for all branches. This filter is closing down. To receive commit notifications for all branches, use the commits:* filter instead. If you have previously set up the commits:all filter, it will continue to work until you update your configuration to use the commits:* filter. Label filters for issue and pull request notifications Label filters allow you to filter notifications based on labels applied to issues and pull requests. When a label filter is set, only notifications for events including the specified label will be sent. For more information about labels, see Managing labels and Filtering and searching issues and pull requests . Currently, it is only possible to have one required label filter per repository. The table below shows which event types are affected by label filters. Event type Is filtered by label Pull requests Issues Comments Reviews Commits/Pushes Branches Creating label filters To create a label filter, use the following command format: Text @GitHub subscribe [OWNER/REPO] +label:"YOUR-LABEL" @GitHub subscribe [OWNER/REPO] +label:"YOUR-LABEL" This creates a required-label filter with the value YOUR-LABEL . Incoming events that support filters are discarded unless they have that label. Updating label filters You can update an existing label filter by specifying a NEW-LABEL value: Text @GitHub subscribe [OWNER/REPO] +label:"NEW-LABEL" @GitHub subscribe [OWNER/REPO] +label:"NEW-LABEL" This will replace the "YOUR-LABEL" filter with the "NEW-LABEL" filter. Removing label filters You can remove an existing label filter by using the unsubscribe command with the +label option: Text @GitHub unsubscribe [OWNER/REPO] +label:"NEW-LABEL" @GitHub unsubscribe [OWNER/REPO] +label:"NEW-LABEL" This will remove the "NEW-LABEL" filter, and the channel will receive all notifications for the subscribed events without any label filtering. Viewing active label filters To view the currently active label filters for a channel, use the following command: Text @GitHub subscribe list features @GitHub subscribe list features Valid filters The GitHub app in Teams supports the most common special characters for label filters, including all emojis that Teams and GitHub provide as standard. Rarely, you may encounter a label that contains a special character that is not supported. For example, any multibyte character not encoded as :foo: , or labels using the , character may not work as expected. GitHub Actions workflow notifications You can subscribe to GitHub Actions workflow run notifications from your channel or personal app using "workflows" feature, using the format @GitHub subscribe OWNER/REPO workflows . When you are subscribed to "workflows", the following functionality is available: * You will get notified when a new workflow run is triggered. * You can track the approval notifications as a reply in the thread and you can approve the notifications directly from the channel or personal app. * Once the workflow is completed, you will get an update as a reply in the thread so that you can see the complete context and history of the workflow run. * If something fails, you can choose to rerun the workflow in place and you can also enable debug logs if needed. Note After March 10, 2025 and for GitHub Enterprise Server version 3.17 onwards, you will no longer be notified about the progress of individual workflow jobs. See the GitHub changelog for more details. Workflow notification filters You can filter workflow notifications by using the following options: Filter Description name Filter by the name of the workflow. actor Filter by the user who triggered the workflow. branch Filter by the branch the workflow is running on. In cases where the pull_request event is included, the branch will be the target branch the pull request is created for. event Filter by the event that triggered the workflow (e.g., push, pull_request). You can configure workflow notification filters with the following format: Text @GitHub subscribe OWNER/REPO workflows:{name:"YOUR-WORKFLOW-NAME" event:"WORKFLOW-EVENT" branch:"BRANCH-NAME" actor:"USERNAME"} @GitHub subscribe OWNER/REPO workflows:{name:"YOUR-WORKFLOW-NAME" event:"WORKFLOW-EVENT" branch:"BRANCH-NAME" actor:"USERNAME"} You can also pass multiple values for each filter, separated by commas. For example: Text @GitHub subscribe OWNER/REPO workflows:{name:"YOUR-WORKFLOW-NAME","ANOTHER-WORKFLOW-NAME" event:"WORKFLOW-EVENT","ANOTHER-WORKFLOW-EVENT" branch:"BRANCH-NAME","ANOTHER-BRANCH-NAME" actor:"USERNAME","ANOTHER-USERNAME"} @GitHub subscribe OWNER/REPO workflows:{name:"YOUR-WORKFLOW-NAME","ANOTHER-WORKFLOW-NAME" event:"WORKFLOW-EVENT","ANOTHER-WORKFLOW-EVENT" branch:"BRANCH-NAME","ANOTHER-BRANCH-NAME" actor:"USERNAME","ANOTHER-USERNAME"} By default, when you configure workflow notifications without passing any filters, it is configured for workflows triggered via pull requests targeting your default branch. You can pass one or multiple entries. You can unsubscribe from workflow notifications using the command: @GitHub unsubscribe OWNER/REPO workflows . Note To receive GitHub Actions notifications in Teams, the GitHub app requires additional permissions. When you attempt to subscribe to workflows for the first time, you will be prompted to grant these permissions. Deployment notifications You can also configure separate deployment notifications. These deployments can happen from GitHub Actions or from external sources using the deployments API. See REST API endpoints for deployments . You can subscribe or unsubscribe to deployment notifications using the following commands: Text @GitHub subscribe OWNER/REPO deployments @GitHub unsubscribe OWNER/REPO deployments @GitHub subscribe OWNER/REPO deployments @GitHub unsubscribe OWNER/REPO deployments Note If you are using GitHub Actions and want to track your deployments to environments, the workflows feature is recommended, as it provides a more complete picture and the ability to approve your deployments directly from Teams. Back to top Help and support Was this Doc helpful? Yes No Help us make GitHub Docs great! All Docs are open source. See something that's wrong or unclear? Submit a pull request. Make a contribution Still need help? Ask the GitHub community Contact support Expert services Blog GitHub Inc. © 2026 Terms Privacy Status Pricing