Skip to content

docs: Add docs about backported commit guidelines #14750

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
mydea merged 2 commits into from
Dec 17, 2024
Merged

docs: Add docs about backported commit guidelines #14750

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8b9811b
docs: Add docs about backported commit guidelines
mydea Dec 17, 2024
a0e1452
Update docs/commit-issue-pr-guidelines.md
mydea Dec 17, 2024
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
9 changes: 9 additions & 0 deletions docs/commit-issue-pr-guidelines.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,15 @@ and committed as such onto `develop`.
Please note that we cannot _enforce_ Squash Merge due to the usage of Gitflow (see below). Github remembers the last
used merge method, so you'll need to make sure to double check that you are using "Squash and Merge" correctly.

## Backporting PRs/Commits

If you want to backport a release to a previous major version, make sure to reflect this in the PR/commit title.
The name should have the backported major as a scope prefix. For example:

```
feat(v8/core): Set custom transaction source for event processors (#5722)
```

## Gitflow

We use [Gitflow](https://docs.github.com/en/get-started/quickstart/github-flow) as a branching model.
Expand Down
Loading