Alya Abbott
Alya Abbott
You don't need to post screenshots of code -- that's never a good way to review it.
You need to put updated screenshots in the PR description, making sure the text exactly follows the spec in the issue. Include examples with 0, 1 and more messages.
Please clean up your commit history and post again to request a review. See [here](https://zulip.readthedocs.io/en/latest/contributing/commit-discipline.html) for guidelines.
@pratik-pc Are you up for doing an initial review on this one?
@Aditya8840 If you feel that you need feedback on your approach, please post a specific question in the [Zulip development community](https://zulip.com/development-community/). Be sure to follow https://zulip.readthedocs.io/en/latest/contributing/asking-great-questions.html. Thanks!
@shuklamaneesh23 have you reviewed the contributor guide instructions for how to claim an issue? > Has the API endpoint been modified to accommodate the above frontend change? This is up...
OK, in that case you need to follow the instructions in the contributor guide for how to ask for another issue to be assigned to you.
@timabbott are you reviewing this PR, or would you like someone else to take a look first?
@userAdityaa you need to focus on getting your 12 open PRs ready to merge, rather than picking up new issues. @Kartikay5849 assigning this back to you, in case you're still...
Your screenshots should also demonstrate that there's no tooltip for a short channel name. Thanks!