Add new backport labels to dev docs (#137418)

A few functional labels have been recently added to GH, which drive the
behavior of automatic backports:
- `backport:prev-minor`
- `backport:prev-major`
- `backport:all-open`

The [dev
docs](https://docs.elastic.dev/kibana-dev-docs/contributing/github)
contain an overview of the different labels that we find on GH, but
these were missing.

The goal of this PR is to ensure the documentation is up to date.

Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
This commit is contained in:
Gerard Soldevila 2022-12-16 21:45:53 +01:00 committed by GitHub
parent d92e2f90bf
commit a2036f0ecf
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -205,10 +205,12 @@ it's notable and affects our users) and which section it appears in. For example
- `release_node:plugin_api_changes`: Specifies a changes to the plugin API and adds the PR to the Plugin API changes page in the Developer Guide
- `release_note:skip`: Omits the PR from release notes
These labels related to backporting PRs:
The following labels are related to backporting PRs:
- `auto-backport`: Automatically backport this PR (to the branches related to
version labels) after it's merged
- `backport`: This PR was backported
- `backport:skip`: This PR does not require backporting
version labels) after it's merged. Requires adding desired target versions labels.
- `backport:prev-minor`: Automatically backport to one lower minor version.
- `backport:prev-major`: Automatically backport to the latest minor version of one lower major version.
- `backport:all-open`: Automatically backport to all generally available versions. This functionally is equivalent to backport:prev-major at the time of writing.
- `backport:skip`: This PR does not require backporting.
- `backport`: This PR was backported (added by CI).