-
Notifications
You must be signed in to change notification settings - Fork 5.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
privilege: add restricted read only #25340
Conversation
No release note, Please follow https://github.com/pingcap/community/blob/master/contributors/release-note-checker.md |
5dedd2a
to
a410b9a
Compare
No release note, Please follow https://github.com/pingcap/community/blob/master/contributors/release-note-checker.md |
a410b9a
to
73c6dae
Compare
No release note, Please follow https://github.com/pingcap/community/blob/master/contributors/release-note-checker.md |
73c6dae
to
d3dc76a
Compare
No release note, Please follow https://github.com/pingcap/community/blob/master/contributors/release-note-checker.md |
d3dc76a
to
475d0cf
Compare
No release note, Please follow https://github.com/pingcap/community/blob/master/contributors/release-note-checker.md |
10b3cde
to
7f1b45c
Compare
428880c
to
c0b0dca
Compare
/cc @morgo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, sorry for the delay :-)
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/merge |
1 similar comment
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 3ab22e9
|
1 similar comment
This pull request has been accepted and is ready to merge. Commit hash: 3ab22e9
|
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 9835eb5
|
@ichn-hu do we have a tracking issue for this effort? Or this is the whole task. |
this is the whole task done atomically :) |
@ichn-hu OK. For development task, we may always create an issue for it. And for design and implementation, I"d suggest separate in two PRs. You may ask what if they run almost simultaneously. Well, always the design PR can go into discussion first, and it refers to the feature branch so that we discuss simultaneously. After the design merged, we create a PR from the feature branch to the master. According to this post, @wjhuang2016 should have further ideas. |
What problem does this PR solve?
Issue Number: close #xxx
Problem Summary:
What is changed and how it works?
Proposal: xxx
What"s Changed:
How it Works:
Related changes
pingcap/docs
/pingcap/docs-cn
:Check List
Tests
Side effects
Release note