fix: Debounce releases and skip empty tags in code workflow

[charlesvien]

Problem

Scheduled releases can fire mid stack merge (we all use Graphite) and the workflow crashes trying to create tags that already exist.

Changes

1. Add a debounce check that waits for 15m of commit inactivity before tagging on scheduled releases
2. Re-dispatch the workflow instead of blocking the runner with a long sleep
3. Skip gracefully when the computed tag already exists

How did you test this?

I did not, we should make a simple ACT tooling setup to test this stuff easily.

[charlesvien]

• fix: Downscale large images before attaching #1987
• feat: Show PR and diff status icons on task list items #1986
• fix: Reduce update check interval from 24h to 1h #1985
• fix: Debounce releases and skip empty tags in code workflow #1983 👈 (View in Graphite)
• fix: Fix stacked chevrons in project select dropdowns #1981
• fix: Enrich attachment-only task descriptions for title generation #1980
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Prompt To Fix All With AI

Fix the following 2 code review issues. Work through them one at a time, proposing concise fixes.
---### Issue 1 of 2
.github/scripts/compute-release-tag.sh:41
**`base_tag` output is never consumed**
The script outputs `base_tag=$LATEST_TAG` on stdout, but the workflow only parses `tag=` from `$RESULT` (via `grep '^tag='`). The `base_tag` line goes into `$RESULT` and is silently discarded. Per simplicity rule #4, this is a superfluous part — either remove the `base_tag` echo or consume it in the workflow (e.g. enrich the "Creating tag" log line).
### Issue 2 of 2
.github/scripts/compute-release-tag.test.sh:68-159
**Tests not parameterised**
Every test case repeats the same `setup_repo` → `run_script` → `assert_*` → `teardown_repo` pattern. The team convention is to prefer parameterised tests. A data-driven table of `(description, setup_commands, expected_exit, expected_stdout_contains, expected_stderr_contains)` tuples iterated by a single `run_test` function would eliminate the repetition and make adding new cases trivial.

_{Reviews (1): Last reviewed commit: "Harden test cleanup and TMPDIR fallback" | Re-trigger Greptile}

[jonathanlab]

LGTM, lets try this and see if we like it

[charlesvien]

Merge activity

• May 4, 6:05 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• May 4, 6:18 PM UTC: Graphite rebased this pull request as part of a merge.
• May 4, 6:28 PM UTC: @charlesvien merged this pull request with Graphite.