Skip to content

Stop tracking the generated sql/object_reference--stable.sql - #22

Merged
jnasbyupgrade merged 1 commit into
Postgres-Extensions:masterfrom
jnasbyupgrade:gitignore-generated-stable-sql
Aug 9, 2026
Merged

Stop tracking the generated sql/object_reference--stable.sql#22
jnasbyupgrade merged 1 commit into
Postgres-Extensions:masterfrom
jnasbyupgrade:gitignore-generated-stable-sql

Conversation

@jnasbyupgrade

Copy link
Copy Markdown
Contributor

Summary

  • sql/object_reference--stable.sql is regenerated from sql/object_reference.sql on every build (stable is a build-time literal, not a frozen release) — committing it just duplicates content that can drift from its own source.
  • Added it to .gitignore, untracked it (git rm --cached), and updated the neighboring comment to note it's the one exception to "version files are committed."

Verified make sql/object_reference--stable.sql still regenerates it correctly and it stays untracked afterward.

Heads up: PRs #17/#18 (already open, on top of #5) also touch this file — merging this one first means they'll need a small rebase to drop it from their own diffs (their content is unaffected, make regenerates it the same way).

🤖 Generated with Claude Code

'stable' is a build-time literal, regenerated from sql/object_reference.sql
on every build -- unlike a real frozen release, committing it just
duplicates content that can drift from its own source.
@jnasbyupgrade
jnasbyupgrade merged commit ba62345 into Postgres-Extensions:master Aug 9, 2026
1 check failed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant