Regarding the use of Sider by developers without assigned seats

We have been operating Sider on a model where organizations purchase and assign seats based on the number of developers who need to perform Pull Request analysis of private repositories. However, there has been an issue where even developers who were not assigned seats could trigger analysis on Pull Requests. We have now fixed that issue.

For private repositories, the following restrictions will be imposed on developers who are not assigned seats in Sider:

  1. Pull Requests opened by developers without a seat will not be analyzed.
  2. Developers without a seat will not be able to access the analysis results screen.

(Restriction #2 had already been implemented, but Restriction #1 was not previously enforced)

Please purchase and assign seats for all developers who need to analyze Pull Requests with Sider (there is no need to assign seats to those who do not need access to Sider’s analysis).

If Sider is configured as a Required status check and Sider analysis is not performed, it may continue to remain in a state awaiting status check. In this case, please check the repository settings.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.