The checkout step in .gitea/workflows/check.yml now sets fetch-depth: 0. By default the checkout action clones shallow and fetches no tags, so the version the build takes from git describe --tags --always (#166) would be a bare commit even on a tagged commit. REPO_POLICIES.md asks this of any repo that takes its version from the tags. A short comment above the setting says why it is there. TODO.md has its Completed Steps entry.
Nothing else in the workflow changes; whether it keeps its script/docker-smoke step is #203.
Disclosures:
Not verified on a CI runner: no workflow run was watched, and the repo has no tags yet, so the tag in the version can first be seen once one is pushed.
No test: the only way to test a workflow setting is code that reads the file, which this repo's rules rule out.
README.md is unchanged: it does not describe the CI checkout.
Model: opus-5-5
The checkout step in `.gitea/workflows/check.yml` now sets `fetch-depth: 0`. By default the checkout action clones shallow and fetches no tags, so the version the build takes from `git describe --tags --always` (https://git.eeqj.de/sneak/pixa/issues/166) would be a bare commit even on a tagged commit. `REPO_POLICIES.md` asks this of any repo that takes its version from the tags. A short comment above the setting says why it is there. `TODO.md` has its Completed Steps entry.
Nothing else in the workflow changes; whether it keeps its `script/docker-smoke` step is https://git.eeqj.de/sneak/pixa/issues/203.
Disclosures:
- Not verified on a CI runner: no workflow run was watched, and the repo has no tags yet, so the tag in the version can first be seen once one is pushed.
- No test: the only way to test a workflow setting is code that reads the file, which this repo's rules rule out.
- `README.md` is unchanged: it does not describe the CI checkout.
Model: opus-5-5
PASSe9f85c4 rebased onto next at ae7c3f2.
Resolved TODO.md locally: this PR's entry goes above the one from #211, at the top of Completed Steps.
Model: opus-5-5
**PASS** `e9f85c4` rebased onto `next` at `ae7c3f2`.
Resolved `TODO.md` locally: this PR's entry goes above the one from https://git.eeqj.de/sneak/pixa/issues/211, at the top of Completed Steps.
Model: opus-5-5
The standard checkout action clones shallow and fetches no tags, so the
version the build takes from `git describe --tags --always` would be a
bare commit even on a tagged commit. The checkout step now sets
`fetch-depth: 0`, as REPO_POLICIES.md asks of a repo that takes its
version from the tags.
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.
The checkout step in
.gitea/workflows/check.ymlnow setsfetch-depth: 0. By default the checkout action clones shallow and fetches no tags, so the version the build takes fromgit describe --tags --always(#166) would be a bare commit even on a tagged commit.REPO_POLICIES.mdasks this of any repo that takes its version from the tags. A short comment above the setting says why it is there.TODO.mdhas its Completed Steps entry.Nothing else in the workflow changes; whether it keeps its
script/docker-smokestep is #203.Disclosures:
README.mdis unchanged: it does not describe the CI checkout.Model: opus-5-5
PASS
e9f85c4rebased ontonextatae7c3f2.Resolved
TODO.mdlocally: this PR's entry goes above the one from #211, at the top of Completed Steps.Model: opus-5-5
e9f85c40dfto3dcd4f6bb7