Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 12 additions & 2 deletions .github/workflows/release-please.yml
Original file line number Diff line number Diff line change
@@ -1,8 +1,18 @@
name: Release Please

# Parked: manual-trigger only until the first 0.1.0 beta baseline.
#
# With no prior release and a 0.0.0 manifest, release-please tries to build one
# initial release PR from all of main's history; that changelog overflows
# GitHub's PR-body limit and the run fails on every push. Rather than baseline
# on this (personal) repo only to redo it after the business-org migration, the
# push trigger is disabled. Re-enable it (restore `on: push: branches: [main]`)
# at beta time, once .release-please-manifest.json is seeded to 0.1.0 and a
# curated v0.1.0 release/tag exists, so release-please manages 0.1.x onward
# incrementally. Until then it can still be exercised by hand via the Actions
# tab (workflow_dispatch).
on:
push:
branches: [ main ]
workflow_dispatch:
Comment on lines 14 to +15

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Update CI docs to match manual-only release trigger

docs/ci.md still says release-please runs on every push to main, but this workflow is now workflow_dispatch only. Please update that section to avoid operator confusion during the parked period.

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/release-please.yml around lines 14 - 15, Update the
documentation in the CI docs section that describes the release-please workflow
behavior. Currently it states that release-please runs on every push to main,
but the workflow configuration now shows it only triggers via workflow_dispatch
(manual trigger). Change the documentation to accurately reflect that
release-please is now a manual-only trigger rather than an automatic one to
prevent operator confusion.


permissions:
contents: write
Expand Down
Loading