Skip to content

test: retarget check (will be closed) - #26

Closed
themightychris wants to merge 3 commits into
mainfrom
test/retarget-check
Closed

themightychris wants to merge 3 commits into
mainfrom
test/retarget-check

Conversation

@themightychris

Copy link
Copy Markdown
Member

Throwaway PR to verify main-retarget and main-guard. Closed immediately after.

themightychris and others added 3 commits October 14, 2026 00:15
… default

Releases had stopped being tagged (v1.4.1 in July, then six PRs with no
tag until the backfill). Wire the JarvusInnovations/infra-components
release-prepare / release-validate / release-publish workflows so pushing
develop opens a Release PR and merging it tags and publishes.

main stays the default branch because `npx skills add` installs from the
default branch and a fresh install should get the latest release, not
unreleased work. Two small workflows cover the one cost of that choice:

- main-guard: a required check on PRs into main that fails unless the head
  is develop (the Release PR) or hotfix/*, and always fails for forks.
- main-retarget: on open, moves any other PR targeting main onto develop
  via the API and leaves a comment. pull_request_target with no checkout.

check.yml now also runs on pushes to develop. README gains a short
Contributing and releases section.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
ci(release): adopt the develop→main Release-PR flow with main kept as default
@themightychris
themightychris deleted the test/retarget-check branch October 14, 2026 04:17
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