Using Github App token to trigger CI for version increment PRs#2157
Using Github App token to trigger CI for version increment PRs#2157dblock merged 1 commit intoopensearch-project:mainfrom
Conversation
Signed-off-by: Vacha Shah <vachshah@amazon.com>
|
Can one of the admins verify this patch? |
| with: | ||
| app_id: ${{ secrets.APP_ID }} | ||
| private_key: ${{ secrets.APP_PRIVATE_KEY }} | ||
| installation_id: 22958780 |
There was a problem hiding this comment.
Do we have any significance of this id?
There was a problem hiding this comment.
Its the installation id of the opensearch-trigger-bot Github App.
There was a problem hiding this comment.
Is it fine to expose it or should we add it in secrets?
There was a problem hiding this comment.
Its fine. Its the same across all repos, we have been using it in backport and dependabot workflows.
There was a problem hiding this comment.
Sounds good. Thanks for answering the questions.
|
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.x 1.x
# Navigate to the new working tree
cd .worktrees/backport-1.x
# Create a new branch
git switch --create backport/backport-2157-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 32a761df2ca117d24ed27a121195c4d8ef9ea1a0
# Push it to GitHub
git push --set-upstream origin backport/backport-2157-to-1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.xThen, 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.2 1.2
# Navigate to the new working tree
cd .worktrees/backport-1.2
# Create a new branch
git switch --create backport/backport-2157-to-1.2
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 32a761df2ca117d24ed27a121195c4d8ef9ea1a0
# Push it to GitHub
git push --set-upstream origin backport/backport-2157-to-1.2
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.2Then, create a pull request where the |
|
Looks like |
I think we should backport it to 1.x, or that workflow won't run when we branch and then release 1.3.0. Would you please do that? Thank you. |
Sure, I added a |
|
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.x 1.x
# Navigate to the new working tree
cd .worktrees/backport-1.x
# Create a new branch
git switch --create backport/backport-2157-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 32a761df2ca117d24ed27a121195c4d8ef9ea1a0
# Push it to GitHub
git push --set-upstream origin backport/backport-2157-to-1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.xThen, create a pull request where the |
1 similar comment
|
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.x 1.x
# Navigate to the new working tree
cd .worktrees/backport-1.x
# Create a new branch
git switch --create backport/backport-2157-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 32a761df2ca117d24ed27a121195c4d8ef9ea1a0
# Push it to GitHub
git push --set-upstream origin backport/backport-2157-to-1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.xThen, 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.x 1.x
# Navigate to the new working tree
cd .worktrees/backport-1.x
# Create a new branch
git switch --create backport/backport-2157-to-1.x
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 32a761df2ca117d24ed27a121195c4d8ef9ea1a0
# Push it to GitHub
git push --set-upstream origin backport/backport-2157-to-1.x
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.xThen, create a pull request where the |
…earch-project#2157) Signed-off-by: Vacha Shah <vachshah@amazon.com>
…earch-project#2157) Signed-off-by: Vacha Shah <vachshah@amazon.com>
* Using Github App token to trigger CI for version increment PRs (#2157) Signed-off-by: Vacha Shah <vachshah@amazon.com> * Fixing the indentation in version.yml (#2163) Signed-off-by: Vacha Shah <vachshah@amazon.com> * Adding signoff option for version workflow PR (#2572) Signed-off-by: Vacha Shah <vachshah@amazon.com>
* Using Github App token to trigger CI for version increment PRs (#2157) Signed-off-by: Vacha Shah <vachshah@amazon.com> * Fixing the indentation in version.yml (#2163) Signed-off-by: Vacha Shah <vachshah@amazon.com> * Adding signoff option for version workflow PR (#2572) Signed-off-by: Vacha Shah <vachshah@amazon.com>
Signed-off-by: Vacha Shah vachshah@amazon.com
Description
Using Github App token to trigger CI on PRs created for version increment from the version.yml workflow. (opensearch-project/common-utils#111 (comment))
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.