qdrant/.github/PULL_REQUEST_TEMPLATE.md at master - qdrant - Gitea: Git with a cup of tea

upstream-archive/qdrant

mirror of https://github.com/qdrant/qdrant.git synced 2026-07-23 11:11:00 -05:00

Files

qdrant-cloud-bot 72be4f9d42 docs: make dev branch requirement more prominent for contributors (#8581 )

Contributors frequently open PRs against master instead of dev.
Add prominent callouts and a root-level CONTRIBUTING.md so the
branch requirement is visible at every step of the contribution flow.

Made-with: Cursor

Co-authored-by: Cursor Agent <agent@cursor.com>

2026-05-08 13:46:00 +02:00

1.1 KiB

Raw Permalink Blame History

All Submissions:

⚠️ PRs must target the dev branch. If your PR targets master, please change the base branch to dev before requesting a review.

My PR targets the dev branch (not master) and my branch was created from dev.
Have you followed the guidelines in our Contributing document?
Have you checked to ensure there aren't other open Pull Requests for the same update/change?

New Feature Submissions:

Does your submission pass tests?
Have you formatted your code locally using cargo +nightly fmt --all command prior to submission?
Have you checked your code using cargo clippy --workspace --all-features command?

Changes to Core Features:

Have you added an explanation of what your changes do and why you'd like us to include them?
Have you written new tests for your core changes, as applicable?
Have you successfully ran tests with your changes locally?