Skip to content
Permalink
Browse files
chore: only reviewer can mark the review resolved (#5994)
  • Loading branch information
spacewander committed Jan 4, 2022
1 parent a2628a6 commit d3bb8f9035b14b35e2d2eccd0959ed00e8fe88e3
Showing 2 changed files with 3 additions and 1 deletion.
@@ -5,13 +5,14 @@
### Pre-submission checklist:

<!--
Please follow the requirements:
Please follow the PR manners:
1. Use Draft if the PR is not ready to be reviewed
2. Test is required for the feat/fix PR, unless you have a good reason
3. Doc is required for the feat PR
4. Use a new commit to resolve review instead of `push -f`
5. If you need to resolve merge conflicts after the PR is reviewed, please merge master but do not rebase
6. Use "request review" to notify the reviewer once you have resolved the review
7. Only reviewer can click "Resolve conversation" to mark the reviewer's review resolved
-->

* [ ] Did you explain what problem does this PR solve? Or what new features have been added?
@@ -48,6 +48,7 @@ Once we've discussed your changes and you've got your code ready, make sure that
* References the original issue in the description, e.g. "Resolves #123".
* Has a [good commit message](http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html).
* Ensure your pull request's title starts from one of the word in the `types` section of [semantic.yml](https://github.com/apache/apisix/blob/master/.github/semantic.yml).
* Follow the [PR manners](https://raw.githubusercontent.com/apache/apisix/master/.github/PULL_REQUEST_TEMPLATE.md)

## Contribution Guidelines for Documentation

0 comments on commit d3bb8f9

Please sign in to comment.