Skip to content

Commit

Permalink
Merge pull request rubygems#3389 from rubygems/remove-bors
Browse files Browse the repository at this point in the history
Remove bors
  • Loading branch information
bronzdoc authored Mar 17, 2020
2 parents a753447 + b0c1efd commit be27b8e
Show file tree
Hide file tree
Showing 4 changed files with 3 additions and 61 deletions.
50 changes: 0 additions & 50 deletions .github/bors.toml

This file was deleted.

11 changes: 2 additions & 9 deletions POLICIES.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,15 +2,8 @@

Contributions to RubyGems are made via GitHub pull requests, which must be
approved by a project committer other than the author. To approve a PR, a
maintainer can leave a comment including the text "@bundlerbot r+", indicating
that they have reviewed the PR and approve it. Bundlerbot will then
automatically create a merge commit, test the merge, and land the PR if the
merge commit passes the tests.

This process guarantees that our release branches always have passing tests,
and reduces siloing of information to a single contributor. For a full list of
possible commands, see [the Bundlerbot
documentation](https://bors.tech/documentation/).
maintainer can use GitHubs PR review feature. After that, if the original author
is happy to merge the PR, she can press the merge button.

## Long-Term Support

Expand Down
2 changes: 1 addition & 1 deletion bundler/doc/POLICIES.md
Original file line number Diff line number Diff line change
Expand Up @@ -66,7 +66,7 @@ Large changes often benefit from being written out more completely, read by othe

### Maintainer team guidelines

Always create pull requests rather than pushing directly to the primary branch. Try to get code review and merge approval from someone other than yourself whenever possible. Always merge using `@bundlerbot` to guarantee the primary branch stays green.
Always create pull requests rather than pushing directly to the primary branch. Try to get code review and merge approval from someone other than yourself whenever possible.

Contributors who have contributed regularly for more than six months (or implemented a completely new feature for a minor release) are eligible to join the maintainer team. Unless vetoed by an existing maintainer, these contributors will be asked to join the maintainer team. If they accept, new maintainers will be given permissions to view maintainer playbooks, accept pull requests, and release new versions.

Expand Down
1 change: 0 additions & 1 deletion bundler/doc/playbooks/TEAM_CHANGES.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,7 +16,6 @@ Interested in adding someone to the team? Here's the process.
- Add them to the [Team page][team] on bundler.io, in the [maintainers list][maintainers]
- Add them to the [list of team members][list] in `contributors.rake`
- Add them to the authors list in `bundler.gemspec`
- Add them to the reviewer list in bundlerbot
- Add them to the owners list on RubyGems.org by running
```
$ gem owner -a EMAIL bundler
Expand Down

0 comments on commit be27b8e

Please sign in to comment.