Skip to content

Update contribution docs #9594

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.

Sign up for GitHub

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

Merged
hsbt merged 2 commits into from
Jun 4, 2026
+5 −5
Merged

Update contribution docs #9594

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
3fc0538
Point contributors to GitHub Discussions instead of the RFC repo
hsbt Jun 4, 2026
db38da8
Describe the rational versioning policy instead of SemVer
hsbt Jun 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions doc/NEW_FEATURES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,14 +2,14 @@

## Substantial Features

To request substantial changes to Bundler or Bundler documentation, please refer to the [RFC repository](https://github.com/rubygems/rfcs). See the [README](https://github.com/rubygems/rfcs/blob/master/README.md) for detailed instructions on the RFC process.
To request substantial changes to Bundler or Bundler documentation, please start a discussion in [GitHub Discussions](https://github.com/rubygems/rubygems/discussions).

## Contributing New Features

To add a new feature to Bundler:

1. **Discuss your idea** - [Open an issue](https://github.com/ruby/rubygems/issues/new) to discuss your proposed feature
2. **Base on master branch** - We follow [SemVer](https://semver.org), so new features go in the master branch only, not old releases
1. **Discuss your idea** - If the goal is already clear, link the existing [issue](https://github.com/rubygems/rubygems/issues) or [discussion](https://github.com/rubygems/rubygems/discussions) that covers it. Otherwise, post your idea in [GitHub Discussions](https://github.com/rubygems/rubygems/discussions) first so it can be talked through
2. **Base on master branch** - Substantial new features go in the master branch only. Releases follow a rational versioning policy: major versions may break existing code, minor versions can change behavior or output while keeping existing functionality working, and tiny versions are mostly bug fixes that may include feature additions
3. **Write tests** - Include at least one test covering your changes in your feature branch
4. **Submit a pull request** - See [PULL_REQUESTS.md](PULL_REQUESTS.md) for detailed guidelines

Expand Down
4 changes: 2 additions & 2 deletions doc/POLICIES.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -93,9 +93,9 @@ avoid breaking things, and we may even intentionally introduce this kind of
cases. So be aware when using internals and ideally get in touch with us
before doing so, so that we can help find the right APIs.

## RFC guidelines
## Discussing large changes

Large changes often benefit from being written out more completely, read by others, and discussed. The [Bundler RFC repo](https://github.com/rubygems/rfcs) is the preferred place for that to happen.
Large changes often benefit from being written out more completely, read by others, and discussed. [GitHub Discussions](https://github.com/rubygems/rubygems/discussions) is the preferred place for that to happen.

## Committer Access

Expand Down
Loading