dump the database to ./backups before applying migrations
run the one-shot migrate service on every deploy instead of relying only on
the api depends_on, so a migration is never skipped
translate the workflow comments to English
- dump the database to ./backups before applying migrations
- run the one-shot migrate service on every deploy instead of relying only on
the api depends_on, so a migration is never skipped
- translate the workflow comments to English
- add users.theme and users.language, exposed in the session and through a
new GET/PATCH /account/preferences endpoint
- replace the global files.is_starred flag with a user_file_stars join table
and backfill existing stars to the file owner
- track chat read state per user (chat_reads) and expose GET /chat/unread for
folder badges
- expose GET /directory listing active users
- drop the unused folders.description column
- let the admin audit log be filtered by user and action, with facets
- add French-keyed i18n with an English dictionary, plus theme and locale
helpers, applied across all pages and components
- account page: theme and language selectors and a two-column layout
- browser: per-folder media type filters and unread chat badges
- admin: audit log filtered by user and action through dropdowns
- global API and type updates to match the new backend endpoints
- dump the database to ./backups before applying migrations
- run the one-shot migrate service on every deploy instead of relying only on
the api depends_on, so a migration is never skipped
- translate the workflow comments to English
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
the api depends_on, so a migration is never skipped
LGTM