-
Notifications
You must be signed in to change notification settings - Fork 11
Comment templates
Richard van der Hoff edited this page Jul 19, 2023
·
12 revisions
Here are some comment templates that you may wish to add to your saved replies.
- Comment:
Thank you for your report.
It seems you're not the only one to have come across this bug, as it's been reported previously. I'm going to close this issue now so we can focus on the older issue. Please watch, vote or comment on that issue if there is any additional information you can provide.
- Close as not planned with comment:
Duplicate of #???
ℹ️ GitHub requires that Duplicate of… is the only text in a comment in order to recognise it as a duplicate.
Thank you for your report. We need some more information from you before our developers can look at it. Please edit your issue to include replies to all sections.
Please comment to let us know when you've had a chance to add more details to the issue.
Thank you for taking the time to tell us about your issue.
I am going to close this issue as it has been resolved in a more recent version of Element and should be available to you soon.
@<username> Thank you for opening an issue. Unfortunately there is not enough information there for me to be able to reproduce it. Please update the description with steps/screenshots/video/more details so our developers can have a look at it.
Hi, I'm going to close this issue for now as there is not enough info here for us to be able to action it. Please feel welcome to reopen or ask me to reopen the issue if you update the description with steps/screenshots/video/more details so our developers can have a look at it.
@<username> Unfortunately I cannot reproduce your issue. Please update your issue with more information. If we don’t hear back from you in a week, we will close the issue as we need to be able to reproduce it before we can fix it.
Thank you for opening an issue. Unfortunately I wasn’t able to reproduce it. If you keep experiencing this defect, please update your description with steps/screenshots/video/more details and add a comment with @<your own username> to let me know that it’s ready to be reopened.
Please use three backticks to enclose big blocks of log output or source code, e.g.
````
```
blah
example
foo
```
````
rather than pasting it directly into a text field.
You should **NOT** manually make edits to the Synapse database at all. Doing so without knowing what you're doing is _highly unsafe_ and we cannot support anyone who has done so without our guidance.
Your best bet is to use the [Delete room admin API](https://matrix-org.github.io/synapse/latest/admin_api/rooms.html#version-2-new-version) with `"purge": true` and `"block": false` to remove your server from any problematic rooms, then try to rejoin them. (Ask in the [Synapse Admins room](https://matrix.to/#/#synapse:matrix.org) if you need assistance using the admin API.) If the problem persists after doing so, please raise a new issue.
We're using Github's issue tracker for bug reports and feature requests. For this kind of support request, please ask in the [Synapse Admins](https://matrix.to/#/#synapse:matrix.org) room. If your homeserver is inoperable at the moment, you can sign up for an account on the Matrix.org homeserver in order to reach the support room.
The following are specific to reviews on pull requests:
Thanks for the PR! However, there are some things that need fixing about it. We encourage you to read [CONTRIBUTING.md](https://github.com/vector-im/element-web/blob/develop/CONTRIBUTING.md) which gives instructions on how to make a good pull request. Looking at the format of other pull requests on the repository should help too. In particular, remember:
* Your PR title will appear in the changelog: make sure it's a good, short description of what your PR does.
* If it fixes an issue, use standard GitHub syntax ("fixes [link to issue]") in the description (not in the title).
* Visual changes needs before and after screenshots.
* Your PR needs DCO signoff. Checking the check box is not sufficient.
We'd welcome a new PR after fixing these issues.
Thanks for your contribution. I'm going to close this for now as the changes requested haven't been made. If you're interested in continuing to work on this please let us know and we can reopen the pull request. Thanks!
Many thanks for this pull request. Unfortunately we're not able to accept this [sign-off](https://matrix-org.github.io/synapse/latest/development/contributing_guide.html#sign-off) as is, because it doesn't include a legally identifiable name. Please either
- update/recreate the sign-off with a legally identifiable name,
- [submit a sign-off privately](https://matrix-org.github.io/synapse/latest/development/contributing_guide.html#private-sign-off) to Matrix.org with a legally identifiable name, or
- close the pull request.
Thank you for your contribution. Please take a look at the [contributing guide](https://github.com/matrix-org/matrix-spec/blob/main/CONTRIBUTING.rst), particularly with respect to [changelog entries](https://github.com/matrix-org/matrix-spec/blob/main/CONTRIBUTING.rst#adding-to-the-changelog) and [sign-off](https://github.com/matrix-org/matrix-spec/blob/main/CONTRIBUTING.rst#sign-off).