Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions .github/workflows/boj-build.yml
Original file line number Diff line number Diff line change
@@ -1,19 +1,17 @@
name: BoJ Server Build Trigger

on:
push:
branches: [ main, master ]
branches: [main, master]
workflow_dispatch:

jobs:
trigger-boj:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v4

- name: Trigger BoJ Server (Casket/ssg-mcp)
run: |
# Send a secure trigger to boj-server to build this repository
curl -X POST "http://boj-server.local:7700/cartridges/ssg-mcp/invoke" -H "Content-Type: application/json" -d "{\"repo\": \"${{ github.repository }}\", \"branch\": \"${{ github.ref_name }}\", \"engine\": \"casket\\"}"}
continue-on-error: true
permissions: read-all

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Avoid granting read-all to this workflow

In .github/workflows/boj-build.yml the job only runs actions/checkout@v4 and a curl command, so contents: read is the only token scope it needs. On repos or orgs that use restricted default GITHUB_TOKEN permissions, explicitly setting permissions: read-all widens the token to every readable scope (issues, PRs, packages, etc.), which increases the blast radius if the runner or one of these steps is compromised.

Useful? React with 👍 / 👎.

Loading