Skip to content

chore(ci): Maximize CI/CD values (Dependabot & Permissions) #1

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.

Sign up for GitHub

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

Merged
hyperpolymath merged 1 commit into from
Mar 18, 2026
Merged

chore(ci): Maximize CI/CD values (Dependabot & Permissions) #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
View file
Open in desktop
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

@chatgpt-codex-connector chatgpt-codex-connector bot Mar 18, 2026

Choose a reason for hiding this comment

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

P2 Badge Avoid widening the workflow token to read-all

If this repository or its org uses the restricted default GITHUB_TOKEN policy, this new workflow-level setting expands trigger-boj to every readable permission even though the job only needs to fetch the repo and send a curl request. That is broader than necessary for the current actions/checkout usage and conflicts with the repo's own least-privilege guidance in docs/architecture/THREAT-MODEL.adoc:125, which calls for per-job scoping after a workflow-level default.

Useful? React with 👍 / 👎.

Loading