chore: untrack mdedit/dist/mdedit.html — every other dist/ is gitignored

mdedit was the only tool whose dist/<tool>.html was force-tracked
(via `git add -f` in the build's stable-cut path). Inconsistent with
every other tool in the repo, where dist/ is fully gitignored. The
build regenerates mdedit/dist/mdedit.html the same way it regenerates
the others, so there's no reason to track it.

Drop the `git add -f` line in build:735 and `git rm --cached` the
file. The on-disk artifact stays put for the dev iteration loop;
only the index entry goes away.
This commit is contained in:
ZDDC 2026-05-04 07:45:26 -05:00
parent df1c32ff54
commit c9f6d08be1
2 changed files with 5 additions and 6242 deletions

11
build
View file

@ -727,14 +727,13 @@ if [ "$RELEASE_CHANNEL" = "stable" ]; then
echo "" echo ""
echo "=== Release commit + tag ===" echo "=== Release commit + tag ==="
# Stage the artifacts that are part of the release. mdedit's dist # Stage the artifacts that are part of the release. dist/ is
# file is the only force-tracked dist artifact today; the others # gitignored everywhere — none of the tools' dist/<tool>.html files
# are gitignored and intentionally not committed. # are tracked. The release commit only carries the bake-in artifacts
# that the binary needs at //go:embed time + the embedded form
# template.
git -C "$SCRIPT_DIR" add "$EMBED_DIR/" \ git -C "$SCRIPT_DIR" add "$EMBED_DIR/" \
"$SCRIPT_DIR/zddc/internal/handler/form.html" "$SCRIPT_DIR/zddc/internal/handler/form.html"
if [ -f "$SCRIPT_DIR/mdedit/dist/mdedit.html" ]; then
git -C "$SCRIPT_DIR" add -f "$SCRIPT_DIR/mdedit/dist/mdedit.html"
fi
if ! git -C "$SCRIPT_DIR" diff --cached --quiet; then if ! git -C "$SCRIPT_DIR" diff --cached --quiet; then
git -C "$SCRIPT_DIR" commit -m "release: v${RELEASE_VERSION} lockstep" git -C "$SCRIPT_DIR" commit -m "release: v${RELEASE_VERSION} lockstep"

6236
mdedit/dist/mdedit.html vendored

File diff suppressed because one or more lines are too long