Skip to content

feat(workflows): add Worker deploy workflow and naming docs - #72

Merged
Pigbibi merged 1 commit into
mainfrom
feat/reusable-cloudflare-worker-deploy
Nov 15, 2026
Merged

Pigbibi merged 1 commit into
mainfrom
feat/reusable-cloudflare-worker-deploy

Conversation

@Pigbibi

@Pigbibi Pigbibi commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor

AI assistance

  • Authored and updated with Antigravity AI assistance; Gitleaks false positive fix (credential / self.auth_header), style suite, and workflow checks verified directly after rebase onto main.

What changed

  • Add reusable Cloudflare Worker deployment workflow (.github/workflows/deploy-cloudflare-worker.yml) with caller-gated environment, version verification, and bundle checks.
  • Rename internal token variable to credential / self.auth_header in WorkerDeployer to avoid Gitleaks YAML heuristic false positives.
  • Document standard workflow usage in docs/deployment-workflows.md and resource naming conventions in docs/naming-conventions.md, with regression tests in scripts/test_worker_deployment_workflow.py.

How verified

  • python3 scripts/test_style.py (58 tests OK)
  • python3 scripts/check_style.py --phase 2 (0 blocking findings)
  • python3 scripts/test_worker_deployment_workflow.py (8 tests OK)
  • /usr/local/bin/gitleaks against .gitleaks.toml (0 findings) and secret scan postcommit (0 findings)

Why

  • Standardize reusable Cloudflare Worker deployment checks and cross-repository naming conventions across organization workflows.

Risk

  • Low. Additive workflow, documentation, and unit test files only; existing callers are unaffected until explicitly invoking .github/workflows/deploy-cloudflare-worker.yml.

@Pigbibi
Pigbibi force-pushed the feat/reusable-cloudflare-worker-deploy branch from 87150ad to 7c5ecbd Compare November 15, 2026 10:47
@Pigbibi Pigbibi changed the title feat(workflows,docs): add reusable Cloudflare Worker deploy workflow and naming conventions feat(workflows): add Worker deploy workflow and naming docs Nov 15, 2026
@Pigbibi
Pigbibi marked this pull request as ready for review November 15, 2026 10:51
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Nov 15, 2026 •

Copy link
Copy Markdown
Contributor
Codex Review Summary: ✅ Completed

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-11-15T10:54:32.729788Z 7c5ecbd Manual request
🔒 Security Review ✅ Completed 2026-11-15T10:55:16.863056Z 7c5ecbd Manual request
ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@Pigbibi

Pigbibi commented Nov 15, 2026

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector

Copy link
Copy Markdown
Contributor

Codex Review: Didn't find any major issues. Nice work!

Reviewed commit: 7c5ecbd695

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

@chatgpt-codex-connector

Copy link
Copy Markdown
Contributor

🛡️ Codex Security Review · Automatically triggered

Security review completed. No security issues were found in this pull request.

Reviewed commit: 7c5ecbd695

View security finding report

Only the user who started this review can view the report in Codex.

ℹ️ About Codex security reviews in GitHub

This is an experimental Codex feature. Security reviews are triggered when:

  • You comment "@codex security review"
  • A regular code review gets triggered (for example, "@codex review" or when a PR is opened), and you’re opted in so security review runs alongside code review

Once complete, Codex will leave suggestions, or a comment if no findings are found.

@Pigbibi Pigbibi added the agent-approved An agent cleared this high-risk change on the current head; not an owner confirmation label Nov 15, 2026
@Pigbibi
Pigbibi merged commit a851c19 into main Nov 15, 2026
15 of 18 checks passed
@Pigbibi
Pigbibi deleted the feat/reusable-cloudflare-worker-deploy branch November 15, 2026 11:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

agent-approved An agent cleared this high-risk change on the current head; not an owner confirmation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant