-
Notifications
You must be signed in to change notification settings - Fork 110
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
Add workflow script for repository management #520
Add workflow script for repository management #520
Conversation
e377948
to
cd8b2cc
Compare
8e7a770
to
60fa4b2
Compare
Oops. Is this error expected?
https://github.com/ruby/gem_rbs_collection/actions/runs/8321546351/job/22767965381?pr=520#step:4:10 |
Yes, it's because this PR has not merged yet. The workflow loads the This error will be recovered after this PR is merged. |
Got it! 👍🏼 |
This PR changes the gem ownership management.
The primary purpose is that the community manages RBS files for gems.
The design doc is here: https://hackmd.io/OBmj4M3tT8SOUXdGjKqntg
Read this document for details.
What
This PR adds GHA workflows to merge PR by contributors and gem reviewers themselves.
Why
Previously, I was the bottleneck of this repository. I needed to review and merge all PRs.
This PR changes the situation. It will achieve real community-driven RBS files. Any contributor can write RBS and become a maintainer without admin permission
How
The main feature is
/merge
comment command. The PR author or Gem Reviewer can trigger this command by commenting/merge
on a PR. It checks the PR is ready to be merged, then merge the PR.For former CODEOWNERS
I'll migrate the CODEOWNERS to another approach. In the new approach, they are called "Gem Reviewers".
You all will be removed from the collaborator of this repository. But your permissions will be migrated to the "Gem Reviewers" one.
The responsibilities have not changed. Thanks for maintaining gems continuously.
The reviewing procedure has small changes. See the CONTRIBUTING.md.
The main change is that a Gem Reviewer can merge a PR related to the maintained gem themselves. Previously, a code owner needed to wait for approval from the repository admin. You can manage RBSs more comfortably.