-
Notifications
You must be signed in to change notification settings - Fork 12
Add Svelte #160
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
base: main
Are you sure you want to change the base?
Add Svelte #160
Conversation
added all images from main
also the button input is optional, when ommitted no button is placed, when not a link must be applied in order for it to redirect
Signed-off-by: Dr. Alto Clef <Preble.louden@gmail.com>
Signed-off-by: fdseilix <113546585+fdseilix@users.noreply.github.com>
Signed-off-by: fdseilix <113546585+fdseilix@users.noreply.github.com>
Signed-off-by: fdseilix <113546585+fdseilix@users.noreply.github.com>
Removed the Docker installation steps to streamline the build process. Signed-off-by: fdseilix <113546585+fdseilix@users.noreply.github.com>
Signed-off-by: fdseilix <113546585+fdseilix@users.noreply.github.com>
Intgrate/docker deploy
Signed-off-by: fdseilix <113546585+fdseilix@users.noreply.github.com>
Removed global installations of @sveltejs/kit and daisyui. Signed-off-by: fdseilix <113546585+fdseilix@users.noreply.github.com>
| runs-on: ubuntu-latest | ||
| steps: | ||
| - name: Checkout repository | ||
| uses: actions/checkout@v4 | ||
|
|
||
| - name: Log in to Container Registry | ||
| uses: docker/login-action@v3 | ||
| with: | ||
| registry: docker.io | ||
| username: ${{ secrets.DOCKER_USERNAME }} | ||
| password: ${{ secrets.DOCKER_PASSWORD }} | ||
|
|
||
| - name: Build Docker images | ||
| run: docker build -f dockerfile -t vfxd9/oakrige-wiki:frontend . | ||
|
|
||
| - name: Push Docker images | ||
| run: docker push vfxd9/oakrige-wiki:frontend |
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI 9 days ago
In general, the fix is to explicitly define a permissions: block that restricts the GITHUB_TOKEN to the minimal scope needed. For this workflow, the job only requires read access to repository contents to allow actions/checkout to work; it does not create releases, push commits, or modify issues/PRs, so contents: read is sufficient and safe. We can set this at the top (workflow) level so it applies to all jobs that lack their own permissions: block.
Concretely, in .github/workflows/Deploy.yml, add a permissions: section right after the name: Deploy line (before on:), with contents: read. This will ensure the GITHUB_TOKEN has read-only access to repository contents and no write access or additional scopes, without altering any existing steps or functionality. No imports or extra definitions are needed because this is purely a YAML configuration change within the workflow file.
-
Copy modified lines R2-R3
| @@ -1,4 +1,6 @@ | ||
| name: Deploy | ||
| permissions: | ||
| contents: read | ||
|
|
||
| on: | ||
| push: |
fixes #152