t
8d5d8af297
CI / check (push) Skipped
CI / e2e (push) Skipped
main is protected (enable_push: false, empty whitelist), so @semantic-release/git's commit-back is rejected by the pre-receive hook -- and it would be rejected *after* the tag was pushed, leaving a tagged release the run then reports as failed. Found by trying to push this branch to main. Whitelisting the CI user was the alternative and is declined: it weakens a protection someone set deliberately and lets a bot push to main without the checks every human PR has to pass. So the release page is the changelog. The changelog plugin now writes a gitignored .release-notes.md, which exists only to carry the notes into gitea-release.sh without interpolating them into a shell command, and CHANGELOG.md is a signpost -- a file claiming to be a changelog while silently never updating is worse than no file. Tags are not protected, so the tag push is unaffected.
91 lines
2.4 KiB
Plaintext
91 lines
2.4 KiB
Plaintext
frontend/dist
|
|
node_modules
|
|
build/bin/
|
|
test_data
|
|
test.db
|
|
|
|
# ── Agent development harness (plan 005) ──
|
|
# playwright-cli scratch output (snapshots, console logs, screenshots)
|
|
.playwright-cli/
|
|
# headless app process state: pid file + captured stdout
|
|
.dev/
|
|
# Playwright spec output: traces, screenshots and videos of failures
|
|
e2e/test-results/
|
|
e2e/playwright-report/
|
|
|
|
# Vitest browser-mode scratch (screenshot diffs, failure captures).
|
|
# The committed baselines under frontend/test/**/__screenshots__ stay.
|
|
frontend/.vitest-attachments/
|
|
|
|
.aider*
|
|
lefthook-local.yml
|
|
|
|
# Profiling artifacts
|
|
trace-*.out
|
|
*.pprof
|
|
|
|
# ── Legacy GSD planning snapshot (replaced by .planning/) ──
|
|
# Kept on disk for reference only; safe to delete once nothing relies on it.
|
|
.gsd
|
|
gsd-session-*.html
|
|
.DS_Store
|
|
Thumbs.db
|
|
*.swp
|
|
*.swo
|
|
*~
|
|
.idea/
|
|
.vscode/
|
|
*.code-workspace
|
|
.env
|
|
.env.*
|
|
!.env.example
|
|
node_modules/
|
|
.next/
|
|
dist/
|
|
# build/ holds v3 build assets and is tracked; only its output is not.
|
|
__pycache__/
|
|
*.pyc
|
|
.venv/
|
|
venv/
|
|
target/
|
|
vendor/
|
|
*.log
|
|
coverage/
|
|
.cache/
|
|
tmp/
|
|
bin/
|
|
|
|
# Task's checksum cache, written by every `wails3 task` run.
|
|
.task/
|
|
|
|
# Generated by build/linux/Taskfile.yml's generate:dotdesktop from
|
|
# build/config.yml on every build, and consumed by the deb/rpm/AppImage
|
|
# packaging tasks that depend on it. A derived file with one source.
|
|
build/linux/yellowjacket.desktop
|
|
|
|
# iOS is not carried. `wails3 update build-assets` regenerates the tree
|
|
# whether or not anything asks for it, so it is ignored rather than
|
|
# deleted-and-rediscovered on every asset refresh, and its includes:
|
|
# entry is dropped from Taskfile.yml.
|
|
#
|
|
# build/android/ *is* carried — see plan 015. Note that `update
|
|
# build-assets` does NOT regenerate it (only `generate build-assets`
|
|
# does, and that rewrites the whole of build/), so the tree is committed
|
|
# and edited by hand like any other source. Only its output is ignored,
|
|
# below.
|
|
build/ios/
|
|
|
|
# Android build output. jniLibs holds the ~30 MB per-ABI c-shared
|
|
# libraries the Go build produces; gen/ and overlay.json are written by
|
|
# `wails3 android overlay:gen`; the rest is Gradle's.
|
|
build/android/app/src/main/jniLibs/
|
|
build/android/app/build/
|
|
build/android/build/
|
|
build/android/.gradle/
|
|
build/android/gen/
|
|
build/android/overlay.json
|
|
|
|
# Written by @semantic-release/changelog purely to carry the release notes
|
|
# into scripts/gitea-release.sh; the release page is the changelog.
|
|
.release-notes.md
|