Frequently Asked Questions

Why don't I see comments?

• If your repository doesn't have a configuration file reviews may not work for all languages in your repository.
• If one of your tool configuration files contains an error, reviews will fail. For example: if your jshint.config file contains a JSON syntax error jshint will fail preventing comments from being posted.
• Make sure your pull requests are a manageable size. The GitHub API has access limits which can affect the number of violations reported. We will batch comments if there are too many violations, but big pull requests may get incomplete responses.

Why can't I see my private repositories?

Private repositories are only visible when you have a paid plan.

Why can't I see a repository on which I'm a collaborator?

Only GitHub repository administrators can enable webhooks, which Stickler CI needs.

How does Sticker CI work on private repositories?

When a private respository is enabled, the stickler-ci GitHub user will be added to your repository as a collaborator. This will require a collaborator seat to be available in your GitHub account/organization. Once added as a collaborator, the bot user will begin reviewing pull requests.

How long does Stickler CI keep my code?

Stickler CI only keeps your code on our servers for the duration of a review. After the comments for a review are posted your code is removed from our servers.

How do I revoke access from Stickler CI?

To stop getting comments on pull requests, you can disable your repository or your repositories page or by revoking the access token Stickler CI uses from the Authorized Applications in GitHub.

Can I use Stickler CI with GitHub Enterprise?

Not currently, but if you are interested in self-hosting contact us and we can figure something out.

Can I use Stickler CI with Bitbucket or Gitlab?

Not currently. If there is enough demand in the future, support may be added.