Skip to content

Push the helm-docs README commit with a comet-ci App token - #42

Merged
GuySaar8 merged 1 commit into
mainfrom
GuySaar8/github-app-token
Oct 22, 2026
Merged

GuySaar8 merged 1 commit into
mainfrom
GuySaar8/github-app-token

Conversation

@GuySaar8

@GuySaar8 GuySaar8 commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

✅ Setup ready: this repo has the comet-ci App credentials, and the comet-ci App can push to main (added as a bypass actor on the branch's ruleset). Ready to review and merge.

Summary

update-readme regenerates the README with helm-docs and pushes it straight to main. The ruleset on main only allows that for bypass actors, which is why it used the org PAT (GH_PAT_TO_ACCESS_GITHUB_API). The push now uses a short-lived comet-ci App token minted just before it, limited to this repo with contents: write.

release (chart-releaser to GHCR) is unchanged and keeps using GITHUB_TOKEN.

Test plan

  • Workflow YAML parses, and no workflow references GH_PAT_TO_ACCESS_GITHUB_API any more
  • After the admin steps: the next chart change on main runs update-readme (README pushed if it changed) and release

🤖 Generated with Claude Code

update-readme pushes the regenerated README straight to main, which the
ruleset on main only allows for bypass actors, so it used the org
PAT. Use a short-lived comet-ci App token limited to this repo
(contents: write) instead. The chart release keeps using GITHUB_TOKEN.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown

📊 Helm Render Diff Summary

Chart charts/s3proxy rendered with Kubernetes 1.29.0. Informational only — this check never fails the PR.

Values File Chart Path Changes Status
test-values/auth-existing-secret.yaml charts/s3proxy - ✅ No Changes
test-values/autoscaling.yaml charts/s3proxy - ✅ No Changes
test-values/azureblob-existing-secret.yaml charts/s3proxy - ✅ No Changes
test-values/azureblob-managed-identity.yaml charts/s3proxy - ✅ No Changes
test-values/azureblob.yaml charts/s3proxy - ✅ No Changes
test-values/b2.yaml charts/s3proxy - ✅ No Changes
test-values/filesystem.yaml charts/s3proxy - ✅ No Changes
test-values/gcs.yaml charts/s3proxy - ✅ No Changes
test-values/ingress.yaml charts/s3proxy - ✅ No Changes
test-values/multi-backend.yaml charts/s3proxy - ✅ No Changes
test-values/openstack-swift.yaml charts/s3proxy - ✅ No Changes
test-values/rackspace.yaml charts/s3proxy - ✅ No Changes
test-values/s3.yaml charts/s3proxy - ✅ No Changes
test-values/tls-existing-secret.yaml charts/s3proxy - ✅ No Changes
test-values/tls.yaml charts/s3proxy - ✅ No Changes
test-values/transient.yaml charts/s3proxy - ✅ No Changes

🎉 No changes detected in any of the tested configurations!

@GuySaar8
GuySaar8 marked this pull request as ready for review October 21, 2026 20:49
@GuySaar8
GuySaar8 merged commit ce44a81 into main Oct 22, 2026
36 checks passed
@GuySaar8
GuySaar8 deleted the GuySaar8/github-app-token branch October 22, 2026 13:53
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.

2 participants