Menu
Open source
Backport commits
Any PRs or commits not on the release branch that you want to include in the release must be backported to the release branch.
Before you begin
Determine the VERSION_PREFIX.
If the release branch already has all the code changes on it, skip this step.
Steps
Pick a PR that you want to backport to
release-VERSION_PREFIX
branch.Add two labels to the PR. First, one of the
product-approved
,type/doc
ortype/bug
appropriately. This is to make sure the PRs that are backported are done with right intention. Secondbackport release-VERSION_PREFIX
label. Now CI should automatically create backport PR to the correct release branch. Example PRNote
CI automation can fail sometimes if there are some merge conflicts in cherry picking the commits. In those cases, the original PR where you added the label should have additional comment explaining how to backport it manually.
Note
The CI job that helps with backporting PR is `.github/workflows/backport.yml`. Useful for debugging purposes.
Repeat the above steps for any PRs that need to be backported.
Was this page helpful?
Related resources from Grafana Labs
Additional helpful documentation, links, and articles:
60 min
Getting started with logging and Grafana Loki
See a demo of the updated features in Loki, and how to create metrics from logs and alert on your logs with powerful Prometheus-style alerting rules.
Video
Essential Grafana Loki configuration settings
This webinar focuses on Grafana Loki configuration including agents Promtail and Docker; the Loki server; and Loki storage for popular backends.
Video
Scaling and securing your logs with Grafana Loki
This webinar covers the challenges of scaling and securing logs, and how Grafana Enterprise Logs powered by Grafana Loki can help, cost-effectively.