# Excluded from every `git archive`, and so from the PGXN bundle `make dist` # produces. Also applies to GitHub's autogenerated "Source code" tarballs, so # never exclude anything needed to build, install or test from source. # # Guard-rail: the pgxn-bundle job in .github/workflows/build-packages.yml # unpacks the zip and compiles it — one line too many fails there, not at upload. # Internal CI. Also the two paths git-filter-repo strips from the GitHub mirror: # without this, the bundle's content depended on which clone produced it. /ci export-ignore /bitbucket-pipelines.yml export-ignore /.github export-ignore /Containerfile export-ignore /.containerignore export-ignore /.valgrind.supp export-ignore /bench_tde.sh export-ignore /.gitignore export-ignore # Maintainer-only: the release procedure, and the tool that regenerates the # Support Matrix in doc/. Neither is of any use to someone installing from a # release bundle; packaging/ is otherwise kept whole (see the note at the end). /PGXN.md export-ignore /packaging/gen-support-matrix.sh export-ignore /packaging/PGDG.md export-ignore # GitHub Wiki source, published to the separate wiki repo. /wiki export-ignore # Suites that only run through ci/scripts (container, Vault or OpenBao needed). # What the PGXN recipe actually uses stays in: # REGRESS = pg_vault_tde_init -> sql/pg_vault_tde_init.sql + expected/ # ISOLATION_OPTS --inputdir -> test/isolation/ # The regression_test*.sql files are not pg_regress tests (no matching expected/) # and DATA does not install them: 273 KB no PGXN user can run. /tap export-ignore /test/tap export-ignore sql/regression_test*.sql export-ignore sql/testing.instructions.md export-ignore # Internal research note, not user documentation. /doc/logical_decoding_research.md export-ignore # packaging/ deliberately stays IN: export-ignore applies to every archive, and # dropping it would leave GitHub's source tarball unable to rebuild .deb/.rpm.