Skip to content

ci: pin explicit permissions on website deploy job - #1935

Closed
CrickCrock28 wants to merge 1 commit into
callstack:mainfrom
harvesthq:fix/workflow-permissions-website
Closed

ci: pin explicit permissions on website deploy job#1935
CrickCrock28 wants to merge 1 commit into
callstack:mainfrom
harvesthq:fix/workflow-permissions-website

Conversation

@CrickCrock28

Copy link
Copy Markdown

The deploy job uses peaceiris/actions-gh-pages with GITHUB_TOKEN to publish to gh-pages, but the workflow has no permissions: block, so it relies on the org default (currently write).

We are flipping the harvesthq org default workflow permissions from write to read (aligning with the BendingSpoons org posture — least-privilege GITHUB_TOKEN). This PR pins the deploy job to the explicit permissions it actually needs (contents: write) so the deploy keeps working unchanged when the org default changes.

Part of the org security-settings alignment tracked in the security team's audit (2026-09).

🤖 Generated with OpenCode (Bsp-agent-beta)

@CrickCrock28

Copy link
Copy Markdown
Author

Opened by mistake — wrong target repo (fork default). Sorry for the noise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant