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

[BUG]: codeql.yml is missing permissions #611

Closed
1 task done
jsoref opened this issue Feb 18, 2024 · 2 comments · Fixed by #612
Closed
1 task done

[BUG]: codeql.yml is missing permissions #611

jsoref opened this issue Feb 18, 2024 · 2 comments · Fixed by #612
Labels
released Type: Bug Something isn't working as documented, or is being fixed

Comments

@jsoref
Copy link
Contributor

jsoref commented Feb 18, 2024

What happened?

https://github.com/check-spelling-sandbox/octokit-types.ts/actions/runs/7915799465

CodeQL-Build
Resource not accessible by integration
CodeQL-Build
Resource not accessible by integration
CodeQL-Build
Resource not accessible by integration
CodeQL-Build
Resource not accessible by integration
CodeQL-Build
Resource not accessible by integration
CodeQL-Build
Resource not accessible by integration
CodeQL-Build
Resource not accessible by integration
CodeQL-Build
Resource not accessible by integration
CodeQL-Build
This run of the CodeQL Action does not have permission to access Code Scanning API endpoints. As a result, it will not be opted into any experimental features. This could be because the Action is running on a pull request from a fork. If not, please ensure the Action has the 'security-events: write' permission. Details: Resource not accessible by integration
CodeQL-Build
Feature flags do not specify a default CLI version. Falling back to the CLI version shipped with the Action. This is 2.16.2.
CodeQL-Build
Resource not accessible by integration

Versions

HEAD

Relevant log output

> Resource not accessible by integration

Code of Conduct

  • I agree to follow this project's Code of Conduct
@jsoref jsoref added Status: Triage This is being looked at and prioritized Type: Bug Something isn't working as documented, or is being fixed labels Feb 18, 2024
Copy link
Contributor

👋 Hi! Thank you for this contribution! Just to let you know, our GitHub SDK team does a round of issue and PR reviews twice a week, every Monday and Friday! We have a process in place for prioritizing and responding to your input. Because you are a part of this community please feel free to comment, add to, or pick up any issues/PRs that are labled with Status: Up for grabs. You & others like you are the reason all of this works! So thank you & happy coding! 🚀

@jsoref jsoref mentioned this issue Feb 18, 2024
4 tasks
@kfcampbell kfcampbell removed the Status: Triage This is being looked at and prioritized label Mar 1, 2024
@octokitbot
Copy link
Collaborator

🎉 This issue has been resolved in version 13.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
released Type: Bug Something isn't working as documented, or is being fixed
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants