-
### Description
My understanding is that if a PR contains a file contained in a particular directory, or a PHP file, GitHub Actions will be triggered and a comment will be added to prompt a backport …
-
From retro: Changes that were made to make the PR validation process more in line with OpenSearch standards made updating the version history more difficult. Specifically, because all old version bran…
-
**Describe the bug**
When backporting a PR that was merged with the "squash and merge" method, and the backporting fails (due to conflicts), the suggestion message doesn't work, because it does not…
-
Tested with:
- Running backport locally:
Merge conflict => Fix locally before it is pushed & PR created
- Running backport via Github action:
Merge conflict
=> Creates a PR for the branches that…
-
### Describe the bug
Any backport PR with merge conflicts will fail CI.
### Steps To Reproduce
Backport a PR that can't be automatically backported (with the `release-2x.xx` label).
### Expect…
-
## What's the task? Please describe
Longhorn repos have below inter-dependencies, so it causes pkg dependency updates tedious or prone to miss. Also, when using Mergify backport a PR that includes …
-
This issue lists Renovate updates and detected dependencies. Read the [Dependency Dashboard](https://docs.renovatebot.com/key-concepts/dashboard/) docs to learn more.
> [!WARNING]
These dependencies …
-
Very recently, Dataproc clusters started to fail at creation, due to an error in the Kafka initialization script, caused by a Debian repository no longer available:
**`https://deb.debian.org/debia…
-
## Context
I have been testing the backport action on https://github.com/Neudrino/magma/pull/6 with the run https://github.com/Neudrino/magma/runs/7803925676?check_suite_focus=true.
## Problem
…
-
According to this: https://github.com/sorenlouv/backport/blob/main/docs/config-file-options.md#fork
The backport action should create the PRs in its own fork, we use it here with a PAT: https://githu…