our sonar organization is bound to our github organization.
New members of the orga who sign-in on sonarcloud are correctly added, but when a member is removed from the github organization, he remains in the members of Sonarcloud.
The binding does not allow to remove manually so it is an issue (former dev are still in the sonar orga).
Thank you for your help.
Template for a good bug report, formatted with Markdown:
- versions used (SonarQube, Scanner, Plugin, and any relevant extension)
- error observed (wrap logs/code around triple quote ``` for proper formatting)
- steps to reproduce
- potential workaround
P.S.: use the #bug:fault sub-category if you’re hitting a specific crash/error , or the #bug:fp sub-category for rules-related behaviour
has anyone met this issue?
Thank you all.
Hi @girton and welcome to our community
Unfortunately, so far the organization bounding does not synchronize automatically when a user is removed from GitHub. But this is definitely in our scope (no ETA yet though).
Thanks for your input
Christophe - PM DevOps platforms
hi @girton ,
As my dear colleagues pointed me out (), it seems like I answered a bit too fast on your post yesterday, sorry.
The auto sync with GitHub works both when you add and when you remove a user. And indeed, when auto-sync is enabled, you cannot manually add/remove users anymore.
In your case, are you sure the project analysed by SonarCloud is not a public one?
Yes it is a private repo.
For some reason I cannot explain now, the gone member was back in github which explains why Sonar kept him. Now that I removed it from the organization manually, Sonar properly removed it from the default members group.
So the problem is solved.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.