You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,6 +10,10 @@ Please search the [issue tracker](https://github.com/getsentry/sentry-python/iss
10
10
11
11
## Submitting Changes
12
12
13
+
Before submitting a pull request, please check whether the issue you're planning to address, if there is one, is assigned to anyone. If you want to help with an issue that already has an assignee, comment on it first to coordinate with the person assigned whether the contribution would make sense before opening a pull request.
14
+
15
+
To make a contribution:
16
+
13
17
- Fork the `sentry-python` repo and prepare your changes.
14
18
- Add tests for your changes to `tests/`.
15
19
- Run tests and make sure all of them pass.
@@ -21,6 +25,18 @@ We will review your pull request as soon as possible. Thank you for contributing
21
25
22
26
You are welcome to use whatever tools you prefer for making a contribution. However, any changes you propose have to be reviewed and tested by you, a human, first, before you submit a pull request with them for the Sentry team to review. If we feel like that didn't happen, we will close the PR outright. For example, we won't review visibly AI-generated PRs from an agent instructed to look for and "fix" open issues in the repo.
23
27
28
+
## Pull Requests
29
+
30
+
All PRs must be created as **drafts**. Non-draft PRs will be automatically converted to draft. Mark your PR as "Ready for review" once:
31
+
32
+
- CI passes
33
+
- The PR description is complete (what, why, and links to relevant issues)
34
+
- You've personally reviewed your own changes
35
+
36
+
A PR should do one thing well. Don't mix functional changes with unrelated refactors or cleanup. Smaller, focused PRs are easier to review, reason about, and revert if needed.
37
+
38
+
For the full set of PR standards, see the [code submission standard](https://develop.sentry.dev/sdk/getting-started/standards/code-submission/#pull-requests).
0 commit comments