Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

ci: remove GITHUB_TOKEN from linter workflow #56

Merged
merged 1 commit into from
Jun 29, 2023

Conversation

nixpanic
Copy link
Contributor

@nixpanic nixpanic commented Jun 28, 2023

Linter logs contain lots of errors like these:

[INFO]   ERROR! Failed to call GitHub Status API!
[INFO]   ERROR:[curl: (22) The requested URL returned error: 403]

By removing the GITHUB_TOKEN, no unknown status updates will be set, so the errors are gone.

@nixpanic nixpanic force-pushed the workflow/super-linter/write branch from 79fd6ab to 24853b0 Compare June 28, 2023 14:38
@nixpanic
Copy link
Contributor Author

These changes are not sufficient yet, the linter still reports

image

@nixpanic nixpanic force-pushed the workflow/super-linter/write branch 3 times, most recently from bc89166 to a67b08a Compare June 28, 2023 15:16
@nixpanic nixpanic changed the title ci: add write permissions for linter workflow ci: remove GITHUB_TOKEN from linter workflow Jun 28, 2023
@nixpanic nixpanic marked this pull request as ready for review June 28, 2023 15:16
Linter logs contain lots of errors like these:

    [INFO]   ERROR! Failed to call GitHub Status API!
    [INFO]   ERROR:[curl: (22) The requested URL returned error: 403]

By removing the `GITHUB_TOKEN` option, only the general result of the
linter is added to the PR status. There is no need to try and set the
status if it always fails, and the warnings can look confusing.

Signed-off-by: Niels de Vos <[email protected]>
@nixpanic nixpanic force-pushed the workflow/super-linter/write branch from a67b08a to d06f3fe Compare June 29, 2023 11:11
@mergify mergify bot merged commit 972be5d into csi-addons:main Jun 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants