mirror of
https://github.com/zulip/zulip.git
synced 2026-06-27 21:01:32 +08:00
f4d98b03d5
Some checks are pending
Code scanning / CodeQL (push) Waiting to run
Zulip production suite / Ubuntu 22.04 production build (push) Waiting to run
Zulip production suite / ${{ matrix.name }} (zulip/ci:bookworm, --test-custom-db, Debian 12 production install with custom db name and user, bookworm) (push) Blocked by required conditions
Zulip production suite / ${{ matrix.name }} (zulip/ci:jammy, , Ubuntu 22.04 production install and PostgreSQL upgrade with pgroonga, jammy) (push) Blocked by required conditions
Zulip production suite / ${{ matrix.name }} (zulip/ci:noble, , Ubuntu 24.04 production install, noble) (push) Blocked by required conditions
Zulip production suite / ${{ matrix.name }} (zulip/ci:bookworm-7.0, 7.0 Version Upgrade, bookworm) (push) Blocked by required conditions
Zulip production suite / ${{ matrix.name }} (zulip/ci:bookworm-8.0, 8.0 Version Upgrade, bookworm) (push) Blocked by required conditions
Zulip production suite / ${{ matrix.name }} (zulip/ci:jammy-6.0, 6.0 Version Upgrade, jammy) (push) Blocked by required conditions
Zulip production suite / ${{ matrix.name }} (zulip/ci:noble-9.0, 9.0 Version Upgrade, noble) (push) Blocked by required conditions
Zulip CI / ${{ matrix.name }} (zulip/ci:bookworm, true, false, Debian 12 (Python 3.11, backend + documentation), bookworm) (push) Waiting to run
Zulip CI / ${{ matrix.name }} (zulip/ci:jammy, false, true, Ubuntu 22.04 (Python 3.10, backend + frontend), jammy) (push) Waiting to run
Zulip CI / ${{ matrix.name }} (zulip/ci:noble, false, false, Ubuntu 24.04 (Python 3.12, backend), noble) (push) Waiting to run
This has the impact of making rebuilding the database in a Zulip development environment, or initializing a new production database, dramatically faster. This was generated by merging the output of `manage.py makemigrations` with an empty migration. Tested using `tools/rebuild-test-database` before and after this change, and comparing the output of `pg_dump -d zulip_test` using Git's diff comparison algorithm. Differences in that SQL dump include: - The actual generated table contents, due to timestamps and the like; this is expected and unrelated to schema. - Orders of fields within tables, which is not significant in SQL. - IDs assigned to tables in the ContentType table, which is expected and not a problem with how that Django table is designed. - Names of generated indexes and constraints; modern Django seems to abbreviate long names differently for these, and it's not obviously possible to configure those used by the `db_index` property. If necessarily, likely this can be converged via a migration filled with `IF EXISTS` rename operations like the one done in zerver/migrations/0246_message_date_sent_finalize_part2.py. - Names of the ~3 sequences related to renamed tables: usertopic/mutedtopic, botconfigdata/botuserconfigdata, realmdomain/realmalias. Probably there's no action required here, but we could do rename operations if desired. |
||
|---|---|---|
| .. | ||
| ci | ||
| documentation_crawler | ||
| droplets | ||
| i18n | ||
| lib | ||
| linter_lib | ||
| node_lib | ||
| oneclickapps | ||
| screenshots | ||
| setup | ||
| test-install | ||
| tests | ||
| zulip-export | ||
| __init__.py | ||
| backport-pull-request | ||
| build-docs | ||
| build-help-center | ||
| build-release-tarball | ||
| cache-zulip-git-version | ||
| check-capitalization | ||
| check-frontend-i18n | ||
| check-issue-labels | ||
| check-openapi | ||
| check-provision | ||
| check-schemas | ||
| check-templates | ||
| check-thirdparty | ||
| clean-branches | ||
| commit-message-lint | ||
| commit-msg | ||
| conf.ini-template | ||
| convert-help-center-docs-to-mdx | ||
| coveragerc | ||
| deploy-branch | ||
| diagnose | ||
| documentation.vnufilter | ||
| duplicate_commits.json | ||
| fetch-contributor-data | ||
| fetch-pull-request | ||
| fetch-rebase-pull-request | ||
| find-unused-css | ||
| lint | ||
| pre-commit | ||
| provision | ||
| push-to-pull-request | ||
| README.md | ||
| rebuild-dev-database | ||
| rebuild-test-database | ||
| release | ||
| release-tarball-exclude.txt | ||
| renumber-migrations | ||
| reset-to-pull-request | ||
| review | ||
| run-codespell | ||
| run-dev | ||
| run-mypy | ||
| run-tsc | ||
| semgrep-py.yml | ||
| setup-git-repo | ||
| show-profile-results | ||
| stop-run-dev | ||
| tail-ses | ||
| test-all | ||
| test-api | ||
| test-backend | ||
| test-documentation | ||
| test-help-documentation | ||
| test-js-with-node | ||
| test-js-with-puppeteer | ||
| test-locked-requirements | ||
| test-migrations | ||
| test-queue-worker-reload | ||
| test-run-dev | ||
| test-tools | ||
| total-contributions | ||
| update-locked-requirements | ||
| update-prod-static | ||
| update-zuliprc-api-field | ||
| upload-release | ||
| webpack | ||
| zanitizer | ||
| zanitizer_config.pm.sample | ||
This directory contains scripts that are used in building, managing,
testing, and other forms of work in a Zulip development environment.
Note that tools that are also useful in production belong in
scripts/ or should be Django management commands.
For more details, see https://zulip.readthedocs.io/en/latest/overview/directory-structure.html.