Dear TiDB Community.
We want to inform you that we will be making some changes to our community infrastructure.
-
As you might know, our TiDB repository now contains a variety of components from previous multiple different repositories, which means that our current LGTM plugin is not able to provide finer control over these components. So we modified the LGTM plugin to accommodate the situation and provide finer control. For the time being, our LGTM plugin will still only be working at the repository level. This means that the only change that will be noticeable to users is that the
/mergecommand will now be replaced with/approve.What’s the difference between
/mergeand/approve?/mergetakes effect at the repository level which means any committer of the repository could merge a PR./approveprovides finer control at directoy level and only the committers of the component could approve. -
Anothe change is due to historical reasons, we were forced to adjust our Github org plan, which unfortunately led to us needing to remove members from PingCAP GitHub org in order to save costs and retain commercial support for some period. Removing people from the Github org will not affect the roles and responsibilities of commiters and reviewers. The TiDB Community repository will continue to be a list of all members. The only major impact of this change is that because people are not in the org, they will be unable to directly add reviewers and assignees in issues/PRs, manually merge changes, or manually add labels.
We are going to gradually apply the changes after the release of TiDB v7.0.0. We apologize for any inconvenience these changes may cause, and we appreciate your patience and support. If you have any questions or concerns, please let us know.