fix(export): untrack the 8 raw postcode export files#1492
Merged
Conversation
These were committed at tiny placeholder sizes during #1039's initial exports wiring (#1403), but the export.yml workflow regenerates them at full size every run — 239 MB json/postcodes.json, 263 MB xml/postcodes.xml, 171 MB yml/postcodes.yml, 123 MB psql/postcodes.sql, 105 MB sqlite/postcodes.sqlite3, 90 MB sql/postcodes.sql, 73 MB sqlserver/postcodes.sql — all over GitHub's 100 MB hard limit. #1490 added .gitignore entries for the same paths but gitignore is inert against tracked files, so the export PR's git push still failed. Untrack here so the gitignore actually applies; large compressed .gz versions continue to ship via GitHub Releases. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
dosubot
Bot
added
the
size:L
There was a problem hiding this comment.
Pull request overview
Removes previously tracked raw postcodes.* export artifacts so the existing .gitignore rules (added in #1490) can actually take effect, preventing the export workflow from attempting to push >100MB files to GitHub.
Changes:
- Deletes tracked placeholder versions of raw postcode exports across JSON/XML/YML/SQL/SQLite/CSV formats.
- Ensures future workflow runs won’t re-add these large raw files to git (they remain generated + ignored;
.gzversions continue to be publishable via Releases per #1490).
Reviewed changes
Copilot reviewed 6 out of 8 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| yml/postcodes.yml | Removes tracked raw YAML postcode export so it remains ignored going forward |
| xml/postcodes.xml | Removes tracked raw XML postcode export so it remains ignored going forward |
| sqlserver/postcodes.sql | Removes tracked raw SQL Server postcode export so it remains ignored going forward |
| sql/postcodes.sql | Removes tracked raw MySQL postcode dump so it remains ignored going forward |
| psql/postcodes.sql | Removes tracked raw PostgreSQL postcode dump so it remains ignored going forward |
| json/postcodes.json | Removes tracked raw JSON postcode export so it remains ignored going forward |
| sqlite/postcodes.sqlite3 | Removes tracked raw SQLite postcode export so it remains ignored going forward |
| csv/postcodes.csv | Removes tracked raw CSV postcode export so it remains ignored going forward |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to #1490. The gitignore entries added there don't apply because the files were already tracked at tiny placeholder sizes (committed during #1039 / #1403 initial exports wiring). The export workflow regenerates them at full size each run, exceeding GitHub's 100 MB hard limit on the PR push.
Untracking lets the existing gitignore (#1490) take effect. Compressed .gz versions continue to publish via GitHub Releases.
Refs: #1039, #1490