(magpie) 01/01: chore(release): gitignore RC build artefacts so they can't be committed

[po...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

potiuk pushed a commit to branch feat-release-gitignore-artefacts
in repository https://gitbox.apache.org/repos/asf/magpie.git

commit 6579262cb8b070d6ac44bcf621c7df03f96d7dc5
Author: Jarek Potiuk <ja...@potiuk.com>
AuthorDate: Wed Jul 8 20:14:54 2026 +0200

    chore(release): gitignore RC build artefacts so they can't be committed
    
    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.
---
 .gitignore                     |  8 ++++++++
 skills/release-rc-cut/SKILL.md | 11 ++++++-----
 2 files changed, 14 insertions(+), 5 deletions(-)

diff --git a/.gitignore b/.gitignore
index d0d597ac..0d56254f 100644
--- a/.gitignore
+++ b/.gitignore
@@ -74,3 +74,11 @@ reassess-*/
 /apache-rat-*/
 rat-report.txt
 rat-stderr.log
+
+# Release-candidate build artefacts (produced by release-rc-cut: the source
+# zip, its detached signature, and its checksum). They are staged to
+# dist/dev via svn, never committed to git — ignore them so a stray
+# `git add` at the repo root can't pick them up.
+/apache-magpie-*-source.zip
+/apache-magpie-*-source.zip.asc
+/apache-magpie-*-source.zip.sha512
diff --git a/skills/release-rc-cut/SKILL.md b/skills/release-rc-cut/SKILL.md
index f29bcc83..ef9f857e 100644
--- a/skills/release-rc-cut/SKILL.md
+++ b/skills/release-rc-cut/SKILL.md
@@ -263,14 +263,15 @@ git push <git-upstream-remote> <version>-<rcN>
 ```
 
 `<git-upstream-remote>` resolves from `git_upstream_remote` in
-`release-management-config.md` — the git remote name pointing at the
-upstream repo (typical: `origin`, `upstream`, `apache`; default `origin`;
-`--remote` overrides). Emit the concrete resolved name, not the placeholder.
+`release-management-config.md` — the upstream repo's git remote name
+(typical `origin`/`upstream`/`apache`; default `origin`; `--remote` overrides). Emit the concrete name.
 
 **Section 2 — Build command.**
 
-The exact `build_command` from `release-build.md`, emitted verbatim with
-a note that it must run at the release tag:
+The exact `build_command` from `release-build.md`, emitted verbatim (run at
+the tag). First **gitignore the RC artefacts** (`<artefact>` + `.asc`/`.sha512`,
+e.g. a committed glob like `*-source.zip*`) so a stray `git add` never commits
+an RC build:
 
 ```text
 # Run at the release tag <version>-<rcN>