Articles on: Synchronization

How to control when Axolo creates Slack channels and reduce channel noise

Axolo opens temporary Slack channels for GitHub pull requests and GitLab merge requests so the author and reviewers can discuss the review in one focused place.


This article explains the documented ways to control when Axolo opens channels and how to reduce noise.


When does Axolo create a Slack channel?


By default, Axolo creates a Slack channel for a new pull request or merge request when:


  1. The repository or GitLab group/project is connected to Axolo.
  2. The repository is active in Axolo.
  3. The PR/MR author is onboarded in Axolo.
  4. Axolo receives the GitHub or GitLab event.
  5. Slack allows Axolo to create and manage the channel.
  6. The PR/MR is not explicitly excluded.


If one of these conditions is missing, Axolo may not create the channel.


Deactivate Axolo for a repository


If you do not want Axolo to open PR channels for a specific repository, deactivate the repository in Axolo repository settings.


When a repository is inactive:


  • Axolo does not open new Slack channels for PRs from this repository.
  • Other active repositories keep working normally.
  • Existing Slack channels are not deleted or archived automatically.


To reactivate the repository, turn it back on in the same repository settings.


Skip channel creation for one PR/MR


For a specific pull request or merge request, you can prevent Axolo from opening a channel by adding _noslackchannel in the PR/MR body or in a label before creating it.


This is useful when one change does not need a dedicated Slack conversation.


Control bot-created PRs/MRs


By default, Axolo does not:


  • open Slack channels when a bot opens a new pull request,
  • send a Slack notification when a bot comments on a pull request,
  • send a Slack notification when a bot reviews a pull request.


You can enable bots in Axolo from the General settings page.


Axolo only lists bots that have opened at least one pull request since your Axolo installation. If a bot is not listed yet, create or wait for a bot PR, then check the setting again.


For more details, read:


Managing bots, service accounts, and automated PRs in Axolo


Reduce team-channel notifications


Team channels are different from PR/MR channels. They announce pull requests in a shared channel like _axolo or a team-specific channel.


In team-channel settings, you can configure when a team channel receives notifications.


For GitHub integrations, team channels can notify when:


  • a team member creates a PR,
  • the team is assigned as reviewer.


For GitLab integrations, team channels continue to notify when team members create pull requests.


Use private PR channels


In Axolo general settings, you can configure Axolo to create private pull request channels instead of public channels.


Private channels reduce Slack history clutter, but people outside the channel cannot access the conversation unless they are invited.


Archive channels automatically


Axolo can automatically archive a PR/MR channel after the pull request is merged or closed.


Auto-archiving is a premium feature. You need a trial or paid plan to activate it.


If your team needs more time after merge or closure, you can configure delayed archiving in Axolo settings.



For high-volume teams, we recommend:


  1. Keep only useful repositories active in Axolo.
  2. Use _noslackchannel for one-off PRs/MRs that do not need a channel.
  3. Configure bot handling instead of letting automated PRs create noise.
  4. Use team-channel notification options for broad team visibility.
  5. Enable auto-archive or delayed archive to keep Slack clean.


If channels are not created


If Axolo is not creating channels when you expect it to, read:


Axolo is not opening channels


Updated on: 11/05/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!