Question: Should assets/changelog.txt be gitignored since CI regenerates it? #231

Closed
opened 2026-05-24 19:03:42 +00:00 by guettlibot · 1 comment
guettlibot commented 2026-05-24 19:03:42 +00:00 (Migrated from codeberg.org)

Context (from #228)

With the fix for issue #228, CI now runs generate-changelog before every Play Store deploy, regenerating assets/changelog.txt from the latest git history. The committed version of assets/changelog.txt is therefore always stale relative to what is actually shipped.

Question

Should assets/changelog.txt be added to .gitignore (and removed from git tracking) since CI always regenerates it?

Options

  1. Keep it committed (current approach): Harmless but the committed file never reflects what was shipped. Developers running the app locally without running generate-changelog first will see an outdated changelog.
  2. Gitignore it and always generate: Removes stale artefact from the repo. Requires generate-changelog to be run before any local build that uses the changelog. The setup task already includes generate-changelog as a dep, so local dev is covered.
  3. Keep it committed but add a comment/note: Document that CI regenerates it so future maintainers understand the discrepancy.
## Context (from #228) With the fix for issue #228, CI now runs generate-changelog before every Play Store deploy, regenerating assets/changelog.txt from the latest git history. The committed version of assets/changelog.txt is therefore always stale relative to what is actually shipped. ## Question Should assets/changelog.txt be added to .gitignore (and removed from git tracking) since CI always regenerates it? ## Options 1. Keep it committed (current approach): Harmless but the committed file never reflects what was shipped. Developers running the app locally without running generate-changelog first will see an outdated changelog. 2. Gitignore it and always generate: Removes stale artefact from the repo. Requires generate-changelog to be run before any local build that uses the changelog. The setup task already includes generate-changelog as a dep, so local dev is covered. 3. Keep it committed but add a comment/note: Document that CI regenerates it so future maintainers understand the discrepancy.
guettlibot commented 2026-05-25 12:43:23 +00:00 (Migrated from codeberg.org)

Already done. assets/changelog.txt is already in .gitignore (line 20) and not tracked in git (git ls-files assets/changelog.txt returns nothing). CI also excludes it from trigger paths (!assets/changelog.txt). Nothing to change. Closing as resolved.

**Already done.** `assets/changelog.txt` is already in `.gitignore` (line 20) and not tracked in git (`git ls-files assets/changelog.txt` returns nothing). CI also excludes it from trigger paths (`!assets/changelog.txt`). Nothing to change. Closing as resolved.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: guettli/sharedinbox#231