-
Notifications
You must be signed in to change notification settings - Fork 26.4k
Main #1978
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
Open
nodoubtz
wants to merge
50
commits into
git:master
Choose a base branch
from
nodoubtz:Main
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Main #1978
Changes from all commits
Commits
Show all changes
50 commits
Select commit
Hold shift + click to select a range
29e95dd
Create azure-webapps-node.yml
nodoubtz 4db67e7
Create python-package-conda.yml
nodoubtz 1e55fb0
Merge branch 'git:master' into master
nodoubtz a7fbfe9
Merge branch 'git:master' into master
nodoubtz 3bd8652
Merge branch 'git:master' into master
nodoubtz 26222a6
Merge branch 'git:master' into master
nodoubtz 09f4901
Create devcontainer.json4
nodoubtz 156417f
Create c-cpp.yml
nodoubtz 607e34e
Create makefile.yml
nodoubtz 2b1086b
Create deno.yml
nodoubtz acd467f
Create cmake-multi-platform.yml
nodoubtz 427a2b2
Create go-ossf-slsa3-publish.yml
nodoubtz 6dc6bc6
Create azure-functions-app-python.yml
nodoubtz 39b6007
Create azure-functions-app-powershell.yml
nodoubtz 3c3485e
Create azure-webapps-python.yml
nodoubtz 5295765
Create azure-functions-app-nodejs.yml
nodoubtz cc8e4c5
Create aws.yml
nodoubtz 499633d
Create google.yml
nodoubtz ebee66f
Create terraform.yml
nodoubtz 057cd4c
Create codeql.yml
nodoubtz ccfbe2f
Create codacy.yml
nodoubtz 103e1b2
Create checkmarx-one.yml
nodoubtz 348ae37
Create checkmarx.yml
nodoubtz 88cab40
Create generator-generic-ossf-slsa3-publish.yml
nodoubtz ac00dcf
Create datadog-synthetics.yml
nodoubtz 6c3ddbe
Create stale.yml
nodoubtz aa03270
Create jekyll-gh-pages.yml
nodoubtz 2ac781c
Create nextjs.yml
nodoubtz 2db6d65
Create mdbook.yml
nodoubtz 0bcf90a
Update README.md
nodoubtz f023cfe
Update README.md
nodoubtz 595f492
Update README.md
nodoubtz a9594f9
Create workflows.yaml
nodoubtz 1fbcd94
Create main.firebase.yaml
nodoubtz 1bf08bc
Create main.callback_url.yaml
nodoubtz 71d547b
Merge branch 'git:master' into master
nodoubtz 5219d87
Add files via upload
nodoubtz df54eb4
Merge branch 'git:master' into Firebase
nodoubtz 90e601b
Merge branch 'git:master' into Main
nodoubtz 043fc91
Update README.md
nodoubtz aea91ab
Update .github/workflows/google.yml
nodoubtz 3590fa4
Merge branch 'Main' into Firebase
nodoubtz 30661b6
Update .github/workflows/jekyll-gh-pages.yml
nodoubtz d0b8489
Merge pull request #7 from nodoubtz/Firebase
nodoubtz e2e9d6b
Merge branch 'git:master' into Main
nodoubtz 0343639
add
nodoubtz 3fdd040
Update README.md
nodoubtz c15097e
add loadLocalImage function to read local image data
nodoubtz 33c5419
Add example custom command to CMakeLists.txt
nodoubtz 43970e9
Add custom command example and local image loading function (#9)
nodoubtz File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
{ | ||
"image": "mcr.microsoft.com/devcontainers/universal:2", | ||
"features": {} | ||
} |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
- await_callback: | ||
call: events.await_callback | ||
args: | ||
callback: ${callback_details} | ||
timeout: 43200 | ||
result: callback_request | ||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,94 @@ | ||
# This workflow will build and push a new container image to Amazon ECR, | ||
# and then will deploy a new task definition to Amazon ECS, when there is a push to the "master" branch. | ||
# | ||
# To use this workflow, you will need to complete the following set-up steps: | ||
# | ||
# 1. Create an ECR repository to store your images. | ||
# For example: `aws ecr create-repository --repository-name my-ecr-repo --region us-east-2`. | ||
# Replace the value of the `ECR_REPOSITORY` environment variable in the workflow below with your repository's name. | ||
# Replace the value of the `AWS_REGION` environment variable in the workflow below with your repository's region. | ||
# | ||
# 2. Create an ECS task definition, an ECS cluster, and an ECS service. | ||
# For example, follow the Getting Started guide on the ECS console: | ||
# https://us-east-2.console.aws.amazon.com/ecs/home?region=us-east-2#/firstRun | ||
# Replace the value of the `ECS_SERVICE` environment variable in the workflow below with the name you set for the Amazon ECS service. | ||
# Replace the value of the `ECS_CLUSTER` environment variable in the workflow below with the name you set for the cluster. | ||
# | ||
# 3. Store your ECS task definition as a JSON file in your repository. | ||
# The format should follow the output of `aws ecs register-task-definition --generate-cli-skeleton`. | ||
# Replace the value of the `ECS_TASK_DEFINITION` environment variable in the workflow below with the path to the JSON file. | ||
# Replace the value of the `CONTAINER_NAME` environment variable in the workflow below with the name of the container | ||
# in the `containerDefinitions` section of the task definition. | ||
# | ||
# 4. Store an IAM user access key in GitHub Actions secrets named `AWS_ACCESS_KEY_ID` and `AWS_SECRET_ACCESS_KEY`. | ||
# See the documentation for each action used below for the recommended IAM policies for this IAM user, | ||
# and best practices on handling the access key credentials. | ||
|
||
name: Deploy to Amazon ECS | ||
|
||
on: | ||
push: | ||
branches: [ "master" ] | ||
|
||
env: | ||
AWS_REGION: MY_AWS_REGION # set this to your preferred AWS region, e.g. us-west-1 | ||
ECR_REPOSITORY: MY_ECR_REPOSITORY # set this to your Amazon ECR repository name | ||
ECS_SERVICE: MY_ECS_SERVICE # set this to your Amazon ECS service name | ||
ECS_CLUSTER: MY_ECS_CLUSTER # set this to your Amazon ECS cluster name | ||
ECS_TASK_DEFINITION: MY_ECS_TASK_DEFINITION # set this to the path to your Amazon ECS task definition | ||
# file, e.g. .aws/task-definition.json | ||
CONTAINER_NAME: MY_CONTAINER_NAME # set this to the name of the container in the | ||
# containerDefinitions section of your task definition | ||
|
||
permissions: | ||
contents: read | ||
|
||
jobs: | ||
deploy: | ||
name: Deploy | ||
runs-on: ubuntu-latest | ||
environment: production | ||
|
||
steps: | ||
- name: Checkout | ||
uses: actions/checkout@v4 | ||
|
||
- name: Configure AWS credentials | ||
uses: aws-actions/configure-aws-credentials@v1 | ||
with: | ||
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }} | ||
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }} | ||
aws-region: ${{ env.AWS_REGION }} | ||
|
||
- name: Login to Amazon ECR | ||
id: login-ecr | ||
uses: aws-actions/amazon-ecr-login@v1 | ||
|
||
- name: Build, tag, and push image to Amazon ECR | ||
id: build-image | ||
env: | ||
ECR_REGISTRY: ${{ steps.login-ecr.outputs.registry }} | ||
IMAGE_TAG: ${{ github.sha }} | ||
run: | | ||
# Build a docker container and | ||
# push it to ECR so that it can | ||
# be deployed to ECS. | ||
docker build -t $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG . | ||
docker push $ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG | ||
echo "image=$ECR_REGISTRY/$ECR_REPOSITORY:$IMAGE_TAG" >> $GITHUB_OUTPUT | ||
|
||
- name: Fill in the new image ID in the Amazon ECS task definition | ||
id: task-def | ||
uses: aws-actions/amazon-ecs-render-task-definition@v1 | ||
with: | ||
task-definition: ${{ env.ECS_TASK_DEFINITION }} | ||
container-name: ${{ env.CONTAINER_NAME }} | ||
image: ${{ steps.build-image.outputs.image }} | ||
|
||
- name: Deploy Amazon ECS task definition | ||
uses: aws-actions/amazon-ecs-deploy-task-definition@v1 | ||
with: | ||
task-definition: ${{ steps.task-def.outputs.task-definition }} | ||
service: ${{ env.ECS_SERVICE }} | ||
cluster: ${{ env.ECS_CLUSTER }} | ||
wait-for-service-stability: true |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,66 @@ | ||
# This workflow will build a Node.js project and deploy it to an Azure Functions App on Windows or Linux when a commit is pushed to your default branch. | ||
# | ||
# This workflow assumes you have already created the target Azure Functions app. | ||
# For instructions see: | ||
# - https://learn.microsoft.com/en-us/azure/azure-functions/create-first-function-vs-code-node | ||
# - https://learn.microsoft.com/en-us/azure/azure-functions/create-first-function-vs-code-typescript | ||
# | ||
# To configure this workflow: | ||
# 1. Set up the following secrets in your repository: | ||
# - AZURE_FUNCTIONAPP_PUBLISH_PROFILE | ||
# 2. Change env variables for your configuration. | ||
# | ||
# For more information on: | ||
# - GitHub Actions for Azure: https://github.com/Azure/Actions | ||
# - Azure Functions Action: https://github.com/Azure/functions-action | ||
# - Publish Profile: https://github.com/Azure/functions-action#using-publish-profile-as-deployment-credential-recommended | ||
# - Azure Service Principal for RBAC: https://github.com/Azure/functions-action#using-azure-service-principal-for-rbac-as-deployment-credential | ||
# | ||
# For more samples to get started with GitHub Action workflows to deploy to Azure: https://github.com/Azure/actions-workflow-samples/tree/master/FunctionApp | ||
|
||
name: Deploy Node.js project to Azure Function App | ||
|
||
on: | ||
push: | ||
branches: ["master"] | ||
|
||
env: | ||
AZURE_FUNCTIONAPP_NAME: 'your-app-name' # set this to your function app name on Azure | ||
AZURE_FUNCTIONAPP_PACKAGE_PATH: '.' # set this to the path to your function app project, defaults to the repository root | ||
NODE_VERSION: '20.x' # set this to the node version to use (e.g. '8.x', '10.x', '12.x') | ||
|
||
jobs: | ||
build-and-deploy: | ||
runs-on: windows-latest # For Linux, use ubuntu-latest | ||
environment: dev | ||
steps: | ||
- name: 'Checkout GitHub Action' | ||
uses: actions/checkout@v4 | ||
|
||
# If you want to use Azure RBAC instead of Publish Profile, then uncomment the task below | ||
# - name: 'Login via Azure CLI' | ||
# uses: azure/login@v1 | ||
# with: | ||
# creds: ${{ secrets.AZURE_RBAC_CREDENTIALS }} # set up AZURE_RBAC_CREDENTIALS secrets in your repository | ||
|
||
- name: Setup Node ${{ env.NODE_VERSION }} Environment | ||
uses: actions/setup-node@v4 | ||
with: | ||
node-version: ${{ env.NODE_VERSION }} | ||
|
||
- name: 'Resolve Project Dependencies Using Npm' | ||
shell: pwsh # For Linux, use bash | ||
run: | | ||
pushd './${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }}' | ||
npm install | ||
npm run build --if-present | ||
npm run test --if-present | ||
popd | ||
|
||
- name: 'Run Azure Functions Action' | ||
uses: Azure/functions-action@v1 | ||
id: fa | ||
with: | ||
app-name: ${{ env.AZURE_FUNCTIONAPP_NAME }} | ||
package: ${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }} | ||
publish-profile: ${{ secrets.AZURE_FUNCTIONAPP_PUBLISH_PROFILE }} # Remove publish-profile to use Azure RBAC | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
# This workflow will deploy a PowerShell project to an Azure Functions App on Windows or Linux when a commit is pushed to your default branch. | ||
# | ||
# This workflow assumes you have already created the target Azure Functions app. | ||
# For instructions see https://learn.microsoft.com/en-us/azure/azure-functions/create-first-function-vs-code-powershell | ||
# | ||
# To configure this workflow: | ||
# 1. Set up the following secrets in your repository: | ||
# - AZURE_FUNCTIONAPP_PUBLISH_PROFILE | ||
# 2. Change env variables for your configuration. | ||
# | ||
# For more information on: | ||
# - GitHub Actions for Azure: https://github.com/Azure/Actions | ||
# - Azure Functions Action: https://github.com/Azure/functions-action | ||
# - Publish Profile: https://github.com/Azure/functions-action#using-publish-profile-as-deployment-credential-recommended | ||
# - Azure Service Principal for RBAC: https://github.com/Azure/functions-action#using-azure-service-principal-for-rbac-as-deployment-credential | ||
# | ||
# For more samples to get started with GitHub Action workflows to deploy to Azure: https://github.com/Azure/actions-workflow-samples/tree/master/FunctionApp | ||
|
||
name: Deploy PowerShell project to Azure Function App | ||
|
||
on: | ||
push: | ||
branches: ["master"] | ||
|
||
env: | ||
AZURE_FUNCTIONAPP_NAME: 'your-app-name' # set this to your function app name on Azure | ||
AZURE_FUNCTIONAPP_PACKAGE_PATH: '.' # set this to the path to your function app project, defaults to the repository root | ||
|
||
jobs: | ||
build-and-deploy: | ||
runs-on: windows-latest # For Linux, use ubuntu-latest | ||
environment: dev | ||
steps: | ||
- name: 'Checkout GitHub Action' | ||
uses: actions/checkout@v4 | ||
|
||
# If you want to use Azure RBAC instead of Publish Profile, then uncomment the task below | ||
# - name: 'Login via Azure CLI' | ||
# uses: azure/login@v1 | ||
# with: | ||
# creds: ${{ secrets.AZURE_RBAC_CREDENTIALS }} # set up AZURE_RBAC_CREDENTIALS secrets in your repository | ||
|
||
- name: 'Run Azure Functions Action' | ||
uses: Azure/functions-action@v1 | ||
id: fa | ||
with: | ||
app-name: ${{ env.AZURE_FUNCTIONAPP_NAME }} | ||
package: ${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }} | ||
publish-profile: ${{ secrets.AZURE_FUNCTIONAPP_PUBLISH_PROFILE }} # Remove publish-profile to use Azure RBAC | ||
Comment on lines
+31
to
+49
Check warningCode scanning / CodeQL Workflow does not contain permissions Medium
Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,65 @@ | ||
# This workflow will build a Python app and deploy it to an Azure Functions App on Linux when a commit is pushed to your default branch. | ||
# | ||
# This workflow assumes you have already created the target Azure Functions app. | ||
# For instructions see https://learn.microsoft.com/en-us/azure/azure-functions/create-first-function-vs-code-python?pivots=python-mode-configuration | ||
# | ||
# To configure this workflow: | ||
# 1. Set up the following secrets in your repository: | ||
# - AZURE_FUNCTIONAPP_PUBLISH_PROFILE | ||
# 2. Change env variables for your configuration. | ||
# | ||
# For more information on: | ||
# - GitHub Actions for Azure: https://github.com/Azure/Actions | ||
# - Azure Functions Action: https://github.com/Azure/functions-action | ||
# - Publish Profile: https://github.com/Azure/functions-action#using-publish-profile-as-deployment-credential-recommended | ||
# - Azure Service Principal for RBAC: https://github.com/Azure/functions-action#using-azure-service-principal-for-rbac-as-deployment-credential | ||
# | ||
# For more samples to get started with GitHub Action workflows to deploy to Azure: https://github.com/Azure/actions-workflow-samples/tree/master/FunctionApp | ||
|
||
name: Deploy Python project to Azure Function App | ||
|
||
on: | ||
push: | ||
branches: ["master"] | ||
|
||
env: | ||
AZURE_FUNCTIONAPP_NAME: 'your-app-name' # set this to your function app name on Azure | ||
AZURE_FUNCTIONAPP_PACKAGE_PATH: '.' # set this to the path to your function app project, defaults to the repository root | ||
PYTHON_VERSION: '3.9' # set this to the python version to use (e.g. '3.6', '3.7', '3.8') | ||
|
||
jobs: | ||
build-and-deploy: | ||
runs-on: ubuntu-latest | ||
environment: dev | ||
steps: | ||
- name: 'Checkout GitHub Action' | ||
uses: actions/checkout@v4 | ||
|
||
# If you want to use Azure RBAC instead of Publish Profile, then uncomment the task below | ||
# - name: 'Login via Azure CLI' | ||
# uses: azure/login@v1 | ||
# with: | ||
# creds: ${{ secrets.AZURE_RBAC_CREDENTIALS }} # set up AZURE_RBAC_CREDENTIALS secrets in your repository | ||
|
||
- name: Setup Python ${{ env.PYTHON_VERSION }} Environment | ||
uses: actions/setup-python@v4 | ||
with: | ||
python-version: ${{ env.PYTHON_VERSION }} | ||
|
||
- name: 'Resolve Project Dependencies Using Pip' | ||
shell: bash | ||
run: | | ||
pushd './${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }}' | ||
python -m pip install --upgrade pip | ||
pip install -r requirements.txt --target=".python_packages/lib/site-packages" | ||
popd | ||
|
||
- name: 'Run Azure Functions Action' | ||
uses: Azure/functions-action@v1 | ||
id: fa | ||
with: | ||
app-name: ${{ env.AZURE_FUNCTIONAPP_NAME }} | ||
package: ${{ env.AZURE_FUNCTIONAPP_PACKAGE_PATH }} | ||
publish-profile: ${{ secrets.AZURE_FUNCTIONAPP_PUBLISH_PROFILE }} # Remove publish-profile to use Azure RBAC | ||
scm-do-build-during-deployment: true | ||
enable-oryx-build: true | ||
Comment on lines
+32
to
+65
Check warningCode scanning / CodeQL Workflow does not contain permissions Medium
Actions job or workflow does not limit the permissions of the GITHUB_TOKEN. Consider setting an explicit permissions block, using the following as a minimal starting point: {contents: read}
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,78 @@ | ||
# This workflow will build and push a node.js application to an Azure Web App when a commit is pushed to your default branch. | ||
# | ||
# This workflow assumes you have already created the target Azure App Service web app. | ||
# For instructions see https://docs.microsoft.com/en-us/azure/app-service/quickstart-nodejs?tabs=linux&pivots=development-environment-cli | ||
# | ||
# To configure this workflow: | ||
# | ||
# 1. Download the Publish Profile for your Azure Web App. You can download this file from the Overview page of your Web App in the Azure Portal. | ||
# For more information: https://docs.microsoft.com/en-us/azure/app-service/deploy-github-actions?tabs=applevel#generate-deployment-credentials | ||
# | ||
# 2. Create a secret in your repository named AZURE_WEBAPP_PUBLISH_PROFILE, paste the publish profile contents as the value of the secret. | ||
# For instructions on obtaining the publish profile see: https://docs.microsoft.com/azure/app-service/deploy-github-actions#configure-the-github-secret | ||
# | ||
# 3. Change the value for the AZURE_WEBAPP_NAME. Optionally, change the AZURE_WEBAPP_PACKAGE_PATH and NODE_VERSION environment variables below. | ||
# | ||
# For more information on GitHub Actions for Azure: https://github.com/Azure/Actions | ||
# For more information on the Azure Web Apps Deploy action: https://github.com/Azure/webapps-deploy | ||
# For more samples to get started with GitHub Action workflows to deploy to Azure: https://github.com/Azure/actions-workflow-samples | ||
|
||
on: | ||
push: | ||
branches: [ "master" ] | ||
workflow_dispatch: | ||
|
||
env: | ||
AZURE_WEBAPP_NAME: your-app-name # set this to your application's name | ||
AZURE_WEBAPP_PACKAGE_PATH: '.' # set this to the path to your web app project, defaults to the repository root | ||
NODE_VERSION: '20.x' # set this to the node version to use | ||
|
||
permissions: | ||
contents: read | ||
|
||
jobs: | ||
build: | ||
runs-on: ubuntu-latest | ||
steps: | ||
- uses: actions/checkout@v4 | ||
|
||
- name: Set up Node.js | ||
uses: actions/setup-node@v4 | ||
with: | ||
node-version: ${{ env.NODE_VERSION }} | ||
cache: 'npm' | ||
|
||
- name: npm install, build, and test | ||
run: | | ||
npm install | ||
npm run build --if-present | ||
npm run test --if-present | ||
|
||
- name: Upload artifact for deployment job | ||
uses: actions/upload-artifact@v4 | ||
with: | ||
name: node-app | ||
path: . | ||
|
||
deploy: | ||
permissions: | ||
contents: none | ||
runs-on: ubuntu-latest | ||
needs: build | ||
environment: | ||
name: 'Development' | ||
url: ${{ steps.deploy-to-webapp.outputs.webapp-url }} | ||
|
||
steps: | ||
- name: Download artifact from build job | ||
uses: actions/download-artifact@v4 | ||
with: | ||
name: node-app | ||
|
||
- name: 'Deploy to Azure WebApp' | ||
id: deploy-to-webapp | ||
uses: azure/webapps-deploy@v2 | ||
with: | ||
app-name: ${{ env.AZURE_WEBAPP_NAME }} | ||
publish-profile: ${{ secrets.AZURE_WEBAPP_PUBLISH_PROFILE }} | ||
package: ${{ env.AZURE_WEBAPP_PACKAGE_PATH }} |
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium