ci: enable GitHub Pages deployments - #4
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4afb547e38
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 91dcf63324
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| group: pages | ||
| cancel-in-progress: true |
There was a problem hiding this comment.
Because this is workflow-level concurrency with a constant group, any manual workflow_dispatch run from a non-main ref enters the same pages group before the job-level if: checks skip both jobs. GitHub Actions concurrency cancels in-progress workflow runs in the same group when cancel-in-progress: true, so a skipped feature-branch dispatch by a write user can abort an active production Pages deployment from main; include github.ref in the group or move concurrency to the deploy job after the main gate.
Useful? React with 👍 / 👎.
1 participant
Summary
Scope
This PR contains only the Pages workflow. The portal implementation remains in #3.