Skip to content

Add single governed execution workflow - #26

Closed
blocksifrdev wants to merge 1 commit into
mainfrom
governed-execution-demo
Closed

blocksifrdev wants to merge 1 commit into
mainfrom
governed-execution-demo

Conversation

@blocksifrdev

Copy link
Copy Markdown
Collaborator

No description provided.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ff5c48fd35

ℹ️ 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".

--arg actor "${{ github.actor }}" \
--arg pr "${{ github.event.pull_request.number }}" \
--arg sha "${{ github.event.pull_request.head.sha }}" \
--argjson paths "$(jq -s . changed.txt | jq -R .)" \

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Build pathsTouched JSON from raw diff output correctly

The --argjson paths expression currently runs jq -s . changed.txt before raw-string conversion, but changed.txt contains plain path lines, not JSON; with any normal file name this jq command exits with a parse error and the Authorize execution step fails under set -euo pipefail. This prevents the governance flow from reaching the authority call for typical PRs.

Useful? React with 👍 / 👎.

Comment on lines +125 to +128
if [ "$DECISION" = "PERMIT" ]; then
echo "✅ Execution permitted"
exit 0
fi

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Allow STEP_UP decisions to pass after manual approval

When the authority returns STEP_UP, the step-up job runs and can receive manual environment approval, but the final gate still only permits DECISION=PERMIT and denies everything else. That makes the step-up path non-functional: even after successful human approval, enforce will always fail for STEP_UP decisions.

Useful? React with 👍 / 👎.

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