How to disable Allstar

If you are receiving unwanted issues created by Allstar, follow the instructions on this page to disable it on your project.

Allstar is run by your own organization, on infrastructure it controls — there is no external service to opt out of. Everything below is a change to configuration files in your organization's repositories, which is the only thing that determines where Allstar acts.

Allstar is highly configurable, so to disable it you need to know:

• Whether Allstar was installed at the organization level or directly on your repository
• Whether Allstar was configured using the opt-in or opt-out strategy (if it was installed at the organization level)

If you already know how Allstar is configured on your organization or repository, follow the instructions for the appropriate configuration:

Disable Allstar, org-level opt-out strategy Disable Allstar, org-level opt-in strategy Disable Allstar, repository level

If you did not set up Allstar yourself and do not know which instructions to follow, contact the administrator who runs it for your organization. Because Allstar runs on your organization's own infrastructure, someone there operates it and can tell you how it is configured — or turn it off for you.

If you are unable to reach them, you can still disable Allstar yourself, but it will take a little more work. Follow these instructions to figure out how Allstar is configured on your project.

Determine how Allstar is configured

  optConfig:
    optOutStrategy:

optConfig:
  optInRepos:
    - other-repo
    - other-repo-two
    - my-repo-name-here
    - yet-another-repo

Disable Allstar, org-level opt-out strategy

These instructions disable Allstar on a repository when Allstar is configured at the organization level using the opt-out strategy.

In the .allstar repository in your organization, open the file named allstar.yaml.

Find the optOutStrategy setting:

optConfig:
  optOutStrategy: true

To opt-out, submit a PR to the .allstar repo, and add the name of your repository to the opt-out list:

optConfig:
  optOutStrategy: true
  optOutRepos:
  - my-repo-name-here

Allstar will be disabled on your repository when the pull request is merged.

Alternative option: with repo-override

This alternative option uses the repo-override setting to avoid the need to submit a pull request to the organization's .allstar repo, but works only if:

• the org-level allstar.yaml config has the line disableRepoOverride: false

or

• the org-level allstar.yaml config file does not the include disableRepoOverride setting (which defaults to false).

If disableRepoOverride is set to true, the following instructions will not work.

To disable Allstar using repo-override, create a file in your repo named .allstar/allstar.yaml with the contents:

optConfig:
  optOut: true

Merge this file to disable Allstar on your repository.

Disable Allstar, org-level opt-in strategy

These instructions disable Allstar on a repository when Allstar is configured at the organization level using the opt-in strategy.

In the org-level .allstar repository, open the allstar.yaml file. Find the optInRepos setting:

optConfig:
  optInRepos:
    - other-repo
    - other-repo-two
    - my-repo-name-here
    - yet-another-repo

Submit a pull request to the .allstar repo that removes your repo name from that list.

When the pull request is merged, Allstar should be disabled on your repository. If you still continue to receive issues, though, it means your project was also opted-in at the repository level. You must also follow the repository-level instructions.

Disable Allstar, repository level

These instructions disable Allstar when it is configured directly on your repository (not at the organization level).

Look in your repository for a file named .allstar/allstar.yaml. It should contain this setting:

optConfig:
  optIn: true

Remove the .allstar/allstar.yaml file from your repository to disable Allstar.