Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Drop GH token from README #46

Merged
merged 1 commit into from
May 23, 2024
Merged

Conversation

bogdanakushnir
Copy link
Contributor

No description provided.

@henryju henryju force-pushed the feature/bogdana/SC-6818-github-token branch from de12c4a to 3073358 Compare May 23, 2024 10:00
@henryju henryju merged commit 4006f66 into master May 23, 2024
8 checks passed
@henryju henryju deleted the feature/bogdana/SC-6818-github-token branch May 23, 2024 10:02
@t3chguy
Copy link

t3chguy commented Dec 4, 2024

Any context for this? Is GITHUB_TOKEN no longer necessary to be passed? https://github.com/SonarSource/sonarcloud-github-action#secrets still refers to GITHUB_TOKEN which just increases confusion. Nothing in the release notes to explain anything https://github.com/SonarSource/sonarcloud-github-action/releases/tag/v2.2

@henryju
Copy link
Member

henryju commented Dec 4, 2024

It might have been necessary a long time ago for PR decoration, but we could not find a use case for it anymore.
We might have left some references that we forgot to clean, we will double-check, thanks (cc @antonioaversa ).

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants