-
Notifications
You must be signed in to change notification settings - Fork 621
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.
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
chore: Apparently github broke docker compose: #3466
Conversation
This PR must be merged before a backport PR will be created. |
4 similar comments
This PR must be merged before a backport PR will be created. |
This PR must be merged before a backport PR will be created. |
This PR must be merged before a backport PR will be created. |
This PR must be merged before a backport PR will be created. |
Pull this into the weekly of this week already. Should be backported everywhere, to not block a bugfix |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-3466-to-release/v1.3 origin/release/v1.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x bdc0079ac2b71b62a2ed9e87e89abb1bb7af59b6 When the conflicts are resolved, stage and commit the changes:
If you have the GitHub CLI installed: # Push the branch to GitHub:
git push --set-upstream origin backport-3466-to-release/v1.3
# Create the PR body template
PR_BODY=$(gh pr view 3466 --json body --template 'Backport bdc0079ac2b71b62a2ed9e87e89abb1bb7af59b6 from #3466{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release/v1.3] chore: Apparently github broke docker compose:' --body-file - --label 'type/bug' --label 'backport' --base release/v1.3 --milestone release/v1.3 --web Or, if you don't have the GitHub CLI installed (we recommend you install it!): # Push the branch to GitHub:
git push --set-upstream origin backport-3466-to-release/v1.3
# Create a pull request where the `base` branch is `release/v1.3` and the `compare`/`head` branch is `backport-3466-to-release/v1.3`.
# Remove the local backport branch
git switch main
git branch -D backport-3466-to-release/v1.3 |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-3466-to-release/v1.4 origin/release/v1.4
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x bdc0079ac2b71b62a2ed9e87e89abb1bb7af59b6 When the conflicts are resolved, stage and commit the changes:
If you have the GitHub CLI installed: # Push the branch to GitHub:
git push --set-upstream origin backport-3466-to-release/v1.4
# Create the PR body template
PR_BODY=$(gh pr view 3466 --json body --template 'Backport bdc0079ac2b71b62a2ed9e87e89abb1bb7af59b6 from #3466{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release/v1.4] chore: Apparently github broke docker compose:' --body-file - --label 'type/bug' --label 'backport' --base release/v1.4 --milestone release/v1.4 --web Or, if you don't have the GitHub CLI installed (we recommend you install it!): # Push the branch to GitHub:
git push --set-upstream origin backport-3466-to-release/v1.4
# Create a pull request where the `base` branch is `release/v1.4` and the `compare`/`head` branch is `backport-3466-to-release/v1.4`.
# Remove the local backport branch
git switch main
git branch -D backport-3466-to-release/v1.4 |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-3466-to-release/v1.5 origin/release/v1.5
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x bdc0079ac2b71b62a2ed9e87e89abb1bb7af59b6 When the conflicts are resolved, stage and commit the changes:
If you have the GitHub CLI installed: # Push the branch to GitHub:
git push --set-upstream origin backport-3466-to-release/v1.5
# Create the PR body template
PR_BODY=$(gh pr view 3466 --json body --template 'Backport bdc0079ac2b71b62a2ed9e87e89abb1bb7af59b6 from #3466{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release/v1.5] chore: Apparently github broke docker compose:' --body-file - --label 'type/bug' --label 'backport' --base release/v1.5 --milestone release/v1.5 --web Or, if you don't have the GitHub CLI installed (we recommend you install it!): # Push the branch to GitHub:
git push --set-upstream origin backport-3466-to-release/v1.5
# Create a pull request where the `base` branch is `release/v1.5` and the `compare`/`head` branch is `backport-3466-to-release/v1.5`.
# Remove the local backport branch
git switch main
git branch -D backport-3466-to-release/v1.5 |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-3466-to-release/v1.6 origin/release/v1.6
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x bdc0079ac2b71b62a2ed9e87e89abb1bb7af59b6 When the conflicts are resolved, stage and commit the changes:
If you have the GitHub CLI installed: # Push the branch to GitHub:
git push --set-upstream origin backport-3466-to-release/v1.6
# Create the PR body template
PR_BODY=$(gh pr view 3466 --json body --template 'Backport bdc0079ac2b71b62a2ed9e87e89abb1bb7af59b6 from #3466{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release/v1.6] chore: Apparently github broke docker compose:' --body-file - --label 'type/bug' --label 'backport' --base release/v1.6 --milestone release/v1.6 --web Or, if you don't have the GitHub CLI installed (we recommend you install it!): # Push the branch to GitHub:
git push --set-upstream origin backport-3466-to-release/v1.6
# Create a pull request where the `base` branch is `release/v1.6` and the `compare`/`head` branch is `backport-3466-to-release/v1.6`.
# Remove the local backport branch
git switch main
git branch -D backport-3466-to-release/v1.6 |
Related: actions/runner-images#9692 (cherry picked from commit bdc0079)
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new branch
git switch --create backport-3466-to-release/v1.7 origin/release/v1.7
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x bdc0079ac2b71b62a2ed9e87e89abb1bb7af59b6 When the conflicts are resolved, stage and commit the changes:
If you have the GitHub CLI installed: # Push the branch to GitHub:
git push --set-upstream origin backport-3466-to-release/v1.7
# Create the PR body template
PR_BODY=$(gh pr view 3466 --json body --template 'Backport bdc0079ac2b71b62a2ed9e87e89abb1bb7af59b6 from #3466{{ "\n\n---\n\n" }}{{ index . "body" }}')
# Create the PR on GitHub
echo "${PR_BODY}" | gh pr create --title '[release/v1.7] chore: Apparently github broke docker compose:' --body-file - --label 'type/bug' --label 'backport' --base release/v1.7 --milestone release/v1.7 --web Or, if you don't have the GitHub CLI installed (we recommend you install it!): # Push the branch to GitHub:
git push --set-upstream origin backport-3466-to-release/v1.7
# Create a pull request where the `base` branch is `release/v1.7` and the `compare`/`head` branch is `backport-3466-to-release/v1.7`.
# Remove the local backport branch
git switch main
git branch -D backport-3466-to-release/v1.7 |
Related: actions/runner-images#9692 (cherry picked from commit bdc0079) Co-authored-by: Christian Simon <simon@swine.de>
Related: actions/runner-images#9692