Some checks failed
Code scanning / CodeQL (push) Failing after 15s
Zulip production suite / Ubuntu 22.04 production build (push) Failing after 26s
Zulip production suite / Debian 12 production install with custom db name and user (push) Has been skipped
Zulip production suite / Ubuntu 22.04 production install and PostgreSQL upgrade with pgroonga (push) Has been skipped
Zulip production suite / Ubuntu 24.04 production install (push) Has been skipped
Zulip production suite / Ubuntu 26.04 production install (push) Has been skipped
Zulip production suite / Debian 13 production install (push) Has been skipped
Zulip production suite / 7.0 Version Upgrade (push) Has been skipped
Zulip production suite / 8.0 Version Upgrade (push) Has been skipped
Zulip production suite / 6.0 Version Upgrade (push) Has been skipped
Zulip production suite / 10.0 Version Upgrade (push) Has been skipped
Zulip production suite / 9.0 Version Upgrade (push) Has been skipped
Zulip production suite / 12.0 Version Upgrade (push) Has been skipped
Zulip production suite / 11.0 Version Upgrade (push) Has been skipped
GitHub Actions Security Analysis with zizmor / zizmor (push) Failing after 3s
Zulip CI / Debian 12 (Python 3.11, backend + documentation) (push) Failing after 26s
Zulip CI / Ubuntu 22.04 (Python 3.10, backend + frontend) (push) Failing after 3s
Zulip CI / Ubuntu 24.04 (Python 3.12, backend) (push) Failing after 25s
Zulip CI / Ubuntu 26.04 (Python 3.14, backend) (push) Failing after 25s
Zulip CI / Debian 13 (Python 3.13, backend) (push) Failing after 28s
Zulip production suite / Required jobs (push) Has been cancelled
Zulip CI / Required jobs (push) Has been cancelled
API Documentation Update Check / check-feature-level-updated (push) Has been cancelled
API Documentation Update Check / notify-if-api-docs-changed (push) Has been cancelled
47 lines
1.9 KiB
Markdown
47 lines
1.9 KiB
Markdown
<!-- Describe your pull request here.-->
|
|
|
|
Fixes: <!-- Issue link, or clear description.-->
|
|
|
|
**How changes were tested:**
|
|
|
|
<!-- If the PR makes UI changes, you must include screenshots.
|
|
Detailed guide: https://zulip.readthedocs.io/en/latest/contributing/presenting-visual-changes.html
|
|
-->
|
|
|
|
**Screenshots and screen captures:**
|
|
|
|
<details>
|
|
<summary>Self-review checklist</summary>
|
|
|
|
<!-- Prior to submitting a PR, follow our step-by-step guide to review your own code:
|
|
https://zulip.readthedocs.io/en/latest/contributing/code-reviewing.html#how-to-review-code -->
|
|
|
|
<!-- Once you create the PR, check off all the steps below that you have completed.
|
|
If any of these steps are not relevant or not completed, leave them unchecked.-->
|
|
|
|
- [ ] [Self-reviewed](https://zulip.readthedocs.io/en/latest/contributing/code-reviewing.html#how-to-review-code) the changes for clarity and maintainability
|
|
(variable names, code reuse, readability, etc.).
|
|
- [ ] Followed the [AI use policy](https://zulip.readthedocs.io/en/latest/contributing/contributing.html#ai-use-policy-and-guidelines).
|
|
|
|
Communicate decisions, questions, and potential concerns.
|
|
|
|
- [ ] Explains differences from previous plans (e.g., issue description).
|
|
- [ ] Highlights technical choices and bugs encountered.
|
|
- [ ] Calls out remaining decisions and concerns.
|
|
- [ ] Automated tests verify logic where appropriate.
|
|
|
|
Individual commits are ready for review (see [commit discipline](https://zulip.readthedocs.io/en/latest/contributing/commit-discipline.html)).
|
|
|
|
- [ ] Each commit is a coherent idea.
|
|
- [ ] Commit message(s) explain reasoning and motivation for changes.
|
|
|
|
Completed manual review and testing of the following:
|
|
|
|
- [ ] Visual appearance of the changes.
|
|
- [ ] Responsiveness and internationalization.
|
|
- [ ] Strings and tooltips.
|
|
- [ ] End-to-end functionality of buttons, interactions and flows.
|
|
- [ ] Corner cases, error conditions, and easily imagined bugs.
|
|
|
|
</details>
|