This may be because Sider does not have access to your organization on GitHub. You can solve this problem by granting Sider access permission to your organization on GitHub shown as the following:
- In your Personal settings on GitHub, proceed
Applications, then open
Authorized OAuth Apps, and select Sider.
- Find your organizations in the
If your organization has migrated to GitHub Apps, you must include your repositories in the "Repository access" section on GitHub. Visit the Sider installation page and select your organization. From there, you can configure repository access for your organization.
Users who can add their repository must have admin permission for the repository. This page helps you to configure your organization registration in Sider.
Check whether GitHub users you would like to assign seats for already have accounts for Sider. If they have already signed up, synchronizing with GitHub will make them appear in organization settings page. You can synchronize with GitHub by trying either of following:
- From the Organization settings page, click the Refresh from GitHub button under the Users tab.
- Click the Begin sync button in the Repository settings page.
Sign in sider.review and select repository page you would like to change settings. And click
Repository Settings in the left column. Then, you can change your repository settings such as the following:
- Selecting analysis tools
- Setting notification
- Switching modes
Please note that you must have a write permission to the repository in order to disable repository.
You can also disable Sider for the repository if you are an admin of the repository.
In many cases, the checkout failure will be resolved by retrying. However, if the error occurs in spite of several retries, the cause of the error is possible that the analyses have been taken a lot of time.
You can ignore specific files to fix the problem. Write the settings to
sider.yml like below:
linter: ignore: - "*.pdf" - "*.mp4"
It might be because of the following situations:
A pull request's author must sign up to Sider and be assigned a seat by organization admins. Unless the condition is satisfied, an analysis never starts. To solve the problem, we recommend you to try the following:
- Assign a seat to the pull request's author who has signed up to Sider.
- Push a new commit to the pull request.
The maximum number of changed files in a pull request is 3,000 in Sider. An analysis never starts if your changed files exceed the limit.
In general, the following solutions are available to solve dependency installation problems:
- If all dependencies are not necessary for analysis, you can specify only the dependencies you need by the
- If private dependencies are necessary for analysis, you need to take the extra steps.
The maximum number of issues is limited to 50,000 per analysis tool. If it exceeds the limitation, no issues are displayed. Here are the recommended ways to prevent such a problem:
- Ignore needless files for analysis via the
- Narrow target files via a tool-specific option of
- Ignore needless files via a tool-specific feature (e.g.
sider.ymlor an analysis tool to fit your project, e.g.