-
Notifications
You must be signed in to change notification settings - Fork 94
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
Modify triggers to push snapshots on all branches #454
Conversation
Signed-off-by: Sayali Gaikawad <[email protected]>
Codecov Report
@@ Coverage Diff @@
## main #454 +/- ##
=========================================
Coverage 73.69% 73.69%
Complexity 804 804
=========================================
Files 125 125
Lines 5219 5219
Branches 662 662
=========================================
Hits 3846 3846
Misses 1087 1087
Partials 286 286 |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.6 2.6
# Navigate to the new working tree
cd .worktrees/backport-2.6
# Create a new branch
git switch --create backport/backport-454-to-2.6
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 1484bff81af8496c93e5f3e9634cb93c1f948750
# Push it to GitHub
git push --set-upstream origin backport/backport-454-to-2.6
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.6 Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.x 2.x
# Navigate to the new working tree
cd .worktrees/backport-2.x
# Create a new branch
git switch --create backport/backport-454-to-2.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 1484bff81af8496c93e5f3e9634cb93c1f948750
# Push it to GitHub
git push --set-upstream origin backport/backport-454-to-2.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.x Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.3 1.3
# Navigate to the new working tree
cd .worktrees/backport-1.3
# Create a new branch
git switch --create backport/backport-454-to-1.3
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 1484bff81af8496c93e5f3e9634cb93c1f948750
# Push it to GitHub
git push --set-upstream origin backport/backport-454-to-1.3
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.3 Then, create a pull request where the |
The backport to
To backport manually, run these commands in your terminal: # Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-2.7 2.7
# Navigate to the new working tree
cd .worktrees/backport-2.7
# Create a new branch
git switch --create backport/backport-454-to-2.7
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 1484bff81af8496c93e5f3e9634cb93c1f948750
# Push it to GitHub
git push --set-upstream origin backport/backport-454-to-2.7
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-2.7 Then, create a pull request where the |
@gaiksaya backport PRs are failed, should we do manual backport? |
Yeah! You can follow above mentioned steps. Thanks! |
…#454) Signed-off-by: Sayali Gaikawad <[email protected]> (cherry picked from commit 1484bff)
…#454) Signed-off-by: Sayali Gaikawad <[email protected]> (cherry picked from commit 1484bff) Signed-off-by: Hailong Cui <[email protected]>
(cherry picked from commit 1484bff) Signed-off-by: Sayali Gaikawad <[email protected]> Signed-off-by: Hailong Cui <[email protected]> Co-authored-by: Sayali Gaikawad <[email protected]>
…#454) (opensearch-project#475) (cherry picked from commit 1484bff) Signed-off-by: Sayali Gaikawad <[email protected]> Signed-off-by: Hailong Cui <[email protected]> Co-authored-by: Sayali Gaikawad <[email protected]> Signed-off-by: AWSHurneyt <[email protected]>
Description
Modify triggers to push snapshots on all branches. See history here: https://github.com/opensearch-project/common-utils/actions/workflows/maven-publish.yml
We had to manually trigger the workflow many times.
Issues Resolved
[List any issues this PR will resolve]
Check List
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.