Found by the review of #207 (#207 (comment)), under the canonical REPO_POLICIES.md re-vendored for #196.
The policy says a repo that embeds a version derived from git tags must set fetch-depth: 0 on its checkout step, because the standard checkout action clones shallow and fetches no tags. pixa's stage that compiles stamps git describe --tags --always (#166), but the checkout step in .gitea/workflows/check.yml has no fetch-depth: 0, so a CI build would stamp a bare commit even on a tagged commit.
Plan: add fetch-depth: 0 to that checkout step, nothing else. Whether the workflow keeps its other step is #203, waiting on the owner; this change does not depend on it.
Model: opus-5-5
Found by the review of https://git.eeqj.de/sneak/pixa/pulls/207 (https://git.eeqj.de/sneak/pixa/pulls/207#issuecomment-125618), under the canonical `REPO_POLICIES.md` re-vendored for https://git.eeqj.de/sneak/pixa/issues/196.
The policy says a repo that embeds a version derived from git tags must set `fetch-depth: 0` on its checkout step, because the standard checkout action clones shallow and fetches no tags. pixa's stage that compiles stamps `git describe --tags --always` (https://git.eeqj.de/sneak/pixa/issues/166), but the checkout step in `.gitea/workflows/check.yml` has no `fetch-depth: 0`, so a CI build would stamp a bare commit even on a tagged commit.
Plan: add `fetch-depth: 0` to that checkout step, nothing else. Whether the workflow keeps its other step is https://git.eeqj.de/sneak/pixa/issues/203, waiting on the owner; this change does not depend on it.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Found by the review of #207 (#207 (comment)), under the canonical
REPO_POLICIES.mdre-vendored for #196.The policy says a repo that embeds a version derived from git tags must set
fetch-depth: 0on its checkout step, because the standard checkout action clones shallow and fetches no tags. pixa's stage that compiles stampsgit describe --tags --always(#166), but the checkout step in.gitea/workflows/check.ymlhas nofetch-depth: 0, so a CI build would stamp a bare commit even on a tagged commit.Plan: add
fetch-depth: 0to that checkout step, nothing else. Whether the workflow keeps its other step is #203, waiting on the owner; this change does not depend on it.Model: opus-5-5
#216 adds
fetch-depth: 0to the checkout step in.gitea/workflows/check.yml, nothing else.Model: opus-5-5