Skip to content

Clarify use of the next banch #408

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
twometresteve merged 1 commit into from
Mar 11, 2026
Merged

Clarify use of the next banch #408

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 4 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,9 +3,10 @@ Contributing
------------

- [Fork](https://help.github.com/articles/fork-a-repo) the [notifier on github](https://github.com/bugsnag/bugsnag-python)
- Create a new branch from `next`
- Commit and push until you are happy with your contribution
- Run the tests
- [Make a pull request](https://help.github.com/articles/using-pull-requests)
- [Make a pull request](https://help.github.com/articles/using-pull-requests) into the `next` branch
- Thanks!

Running the tests
Expand Down Expand Up @@ -90,7 +91,7 @@ If you're on the core team, you can release Bugsnag as follows:

## Making a release

* Create branch for the release
* Create branch for the release from `next`

```
git checkout -b release/v4.x.x
Expand All @@ -108,6 +109,7 @@ If you're on the core team, you can release Bugsnag as follows:
python setup.py sdist bdist_wheel
twine upload dist/*
```
* After the release, create a PR to merge `master` back into `next` to keep the branches in sync.

## Update docs.bugsnag.com

Expand Down
Loading