-
Notifications
You must be signed in to change notification settings - Fork 61
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
Add github workflow for auto release #712
Conversation
Signed-off-by: Ankit Kala <[email protected]>
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #712 +/- ##
============================================
- Coverage 73.34% 73.21% -0.13%
- Complexity 997 998 +1
============================================
Files 141 141
Lines 4637 4637
Branches 519 519
============================================
- Hits 3401 3395 -6
- Misses 911 920 +9
+ Partials 325 322 -3
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
BWC and security test failures are known issues on main |
Signed-off-by: Ankit Kala <[email protected]> (cherry picked from commit 1a470d0)
Signed-off-by: Ankit Kala <[email protected]> (cherry picked from commit 1a470d0)
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-712-to-2.6
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 1a470d0b2d021ead0bcf6b6493780d80f4c234d7
# Push it to GitHub
git push --set-upstream origin backport/backport-712-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 |
Signed-off-by: Ankit Kala <[email protected]> (cherry picked from commit 1a470d0)
Signed-off-by: Ankit Kala <[email protected]> (cherry picked from commit 1a470d0) Co-authored-by: Ankit Kala <[email protected]>
Signed-off-by: Ankit Kala <[email protected]> (cherry picked from commit 1a470d0) Co-authored-by: Ankit Kala <[email protected]>
- uses: ncipollo/release-action@v1 | ||
with: | ||
github_token: ${{ steps.github_app_token.outputs.token }} | ||
bodyFile: release-notes/opensearch.release-notes-${{steps.tag.outputs.tag}}.md |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ankitkala this workflow will fail as the release notes directory points to opensearch structure.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let me fix this in a separate PR.
Description
This change adds the github action to automatically publish a github release based on tags pushed by
opensearch-build
Issues Resolved
#703
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.