# 401 during GH workflow of Gradle sonar task with SonarCloud

**URL:** <https://community.sonarsource.com/t/401-during-gh-workflow-of-gradle-sonar-task-with-sonarcloud/132159>\
**Category:** SonarQube Cloud\
**Tags:** gradle\
**Created:** [December 13, 2024, 6:27pm UTC](https://community.sonarsource.com/t/401-during-gh-workflow-of-gradle-sonar-task-with-sonarcloud/132159 "2024-12-13T18:27:34Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![ascheman](https://dub1.discourse-cdn.com/sonarsource/user_avatar/community.sonarsource.com/ascheman/32/54856_2.png) [@ascheman](https://community.sonarsource.com/u/ascheman)\
**Post date:** [January 5, 2025, 1:39am UTC](https://community.sonarsource.com/t/401-during-gh-workflow-of-gradle-sonar-task-with-sonarcloud/132159/12 "2025-01-05T01:39:20Z")

</div>

Could you elaborate a little more on why you consider allowing anyone to “Execute [the] Analysis” is a bad idea, @Colin?

In this case this is an OSS project. I would like to allow anyone to execute the analysis for their changes. It shouldn’t matter whether they start the Sonar plugin from a PR or from their local machine. We would like to find possible issues as early as possible (and not first merge them).

---

_[View the full topic](https://community.sonarsource.com/t/401-during-gh-workflow-of-gradle-sonar-task-with-sonarcloud/132159)._