Skip to content

chore(release): gitignore RC build artefacts so they can't be committed#789

Merged
potiuk merged 1 commit into
mainfrom
feat-release-gitignore-artefacts
Jul 8, 2026
Merged

chore(release): gitignore RC build artefacts so they can't be committed#789
potiuk merged 1 commit into
mainfrom
feat-release-gitignore-artefacts

Conversation

@potiuk

@potiuk potiuk commented Jul 8, 2026

Copy link
Copy Markdown
Member

Summary

release-rc-cut builds the source artefact (apache-magpie-<version>-source.zip), its detached signature (.asc), and its checksum (.sha512) in the repo root as untracked files. Those get staged to dist/dev via svn and must never be committed to git — but a stray git add . / git commit -a at the wrong moment could pick them up.

This ignores them and documents the guard in the skill.

Changes

  • .gitignore — ignore /apache-magpie-*-source.zip, .asc, and .sha512 (mirrors the existing "Apache RAT working artefacts" pattern already in the file). Verified with git check-ignore that all three RC artefacts now match.
  • skills/release-rc-cut/SKILL.md — Section 2 (Build) now tells the RM to gitignore the RC artefacts first (via a committed glob like *-source.zip*) so adopters get the same protection. Kept SKILL.md at 500 lines (trimmed a line from the tag-command note).

Test plan

  • git check-ignore apache-magpie-0.1.0-source.zip{,.asc,.sha512} → all three ignored.
  • skill-and-tool-validate passes, no new warnings (SKILL.md at 500 lines).

🤖 Generated with Claude Code

release-rc-cut builds the source zip + .asc + .sha512 in the repo root as
untracked files, so a stray `git add .` could commit an RC artefact. Add
ignore rules for them to the repo .gitignore, and add a gitignore-first note
to the release-rc-cut build recipe (Section 2) so adopters do the same.
@potiuk potiuk merged commit 9a54cbb into main Jul 8, 2026
10 checks passed
@potiuk potiuk deleted the feat-release-gitignore-artefacts branch July 8, 2026 18:20
@potiuk potiuk mentioned this pull request Jul 8, 2026
13 tasks
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