PULL ALPHA #422
PULL ALPHA #422
Conversation
add permission documentation
update absolute path func for sourcify WriteFile error
update theme plugin
Bumps [ini](https://github.com/isaacs/ini) from 1.3.5 to 1.3.7. - [Release notes](https://github.com/isaacs/ini/releases) - [Commits](npm/ini@v1.3.5...v1.3.7) Signed-off-by: dependabot[bot] <[email protected]>
Fix CompilationFileSources API interface
Bump ini from 1.3.5 to 1.3.7
Fix vscode bug on deactivation
add support for theia in webview
bump version 0.3.4
lastCompilationResult is what is being returned by getcompilationresult, not a compilationresult
return lastcompilationresult, not a compilationresult
AddAnnotation method added
revert allow_same_origin
Electronplugin
| @@ -0,0 +1,157 @@ | |||
| ## Plugin electon | |||
|
|
|||
| @@ -0,0 +1,157 @@ | |||
| ## Plugin electon | |||
|
|
|||
| How to use the plugin: | |||
There was a problem hiding this comment.
| How to use the plugin: | |
| How to use the plugin: |
| ## Plugin electon | ||
|
|
There was a problem hiding this comment.
| ## Plugin electon | |
| ## Plugin electon | |
| How to use the plugin: | ||
|
|
||
| In electron you | ||
| 1. add the base plugin to a basic engine in electron: ElectronBasePlugin |
There was a problem hiding this comment.
| 1. add the base plugin to a basic engine in electron: ElectronBasePlugin | |
| 1. add the base plugin to a basic engine in electron: ElectronBasePlugin |
| 1. add the base plugin to a basic engine in electron: ElectronBasePlugin | |
| 1. add the base plugin to a basic engine in electron: ElectronBasePlugin |
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: yann300/rebase-pull-requests@master No newline at end of file |
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI about 1 month ago
The correct fix is to explicitly specify permissions at the workflow or job level. Since this workflow uses an action that rebases pull requests, it needs write access to pull requests, and potentially read-only access to contents. Add a permissions block under the root level (recommended so all future jobs inherit) with the following:
permissions:
contents: read
pull-requests: writePlace this directly after the name: and before on: (lines 1-2), or directly after on: (line 6), to apply globally across all jobs. This follows the principle of least privilege, ensuring the GITHUB_TOKEN only has read access to contents and write access to pull requests, nothing else.
| @@ -1,4 +1,7 @@ | ||
| name: Rebase Pull Requests | ||
| permissions: | ||
| contents: read | ||
| pull-requests: write | ||
| on: | ||
| push: | ||
| branches: [master] |
10 participants
PULL ALPHA