Skip to content

Add PR message expectations #295

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
lochhh merged 2 commits into from
Jun 30, 2026
Merged

Add PR message expectations #295

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0dc2e60
Add PR message expectations
adamltyson Jun 30, 2026
310e38f
Fix indentation in development guidelines
lochhh Jun 30, 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
5 changes: 4 additions & 1 deletion docs/source/get-involved/development_guidelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -58,9 +58,12 @@ one operating system.

* We will use [semantic versioning](https://semver.org/) for all projects.

## Pull requests
## Pull requests (PRs)
- Please submit _draft_ pull requests as early as possible (you can still push to the branch once submitted) to
allow for discussion.
- Please ensure that the title of your PR clearly explains its purpose. The "why" is more important than the "how"
(which should be clear from the code and the PR description). We do not use any standards such as
[Conventional Commits](https://www.conventionalcommits.org) so PR titles should not include this metadata.
- One approval of a PR is enough for it to be merged.
- Unless someone approves the PR with optional comments, the PR can be immediately merged by the approving reviewer.
- Please merge via "Squash and Merge" on GitHub to maintain a clean commit history.
Expand Down
Loading