Repository navigation
chore: use global ship-pr and refresh release wording - #185
Merged
Merged
Conversation
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Remove the duplicate local ship-pr skill, retain project review/merge rules in AGENTS.md, and label the release binary as Apple Silicon (arm64).
Why?
Opening both OpenBoot repositories exposed duplicate ship-pr entries. The single global skill now lives in fullstackjam/dotfiles#2. Release notes also listed outdated chip generations.
Testing
go vet ./...passesgo test ./internal/...,make test-unit, andgolangci-lint run ./...passCross-repo checklist
Notes for reviewer
Low risk: no runtime code changes. The two concerns are separate commits. Reverting restores the old skill/template; global installation was verified to expose exactly one skill entry.