Fixes for cmd bot #448
Merged
Fixes for cmd bot #448
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ggwpez
approved these changes
Aug 30, 2024
bkchr
approved these changes
Aug 30, 2024
.github/workflows/cmd.yml
Outdated
| env: | ||
| JOB_NAME: 'cmd' | ||
| PR_BRANCH: ${{ needs.get-pr-branch.outputs.pr-branch }} |
There was a problem hiding this comment.
nowhere, thought to use it but then didn't )) will remove, thanks
mordamax
commented
Aug 30, 2024
|
/merge |
|
Review required! Latest push from author must always be reviewed |
bkchr
approved these changes
Aug 30, 2024
|
/merge |
Auto-Merge-BotCommand `` not recognized. Available commands
For more information see the documentation |
|
Enabled Available commands
For more information see the documentation |
fellowship-merge-bot
bot
merged commit 2d9e568
into
polkadot-fellows:main
46 of 48 checks passed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
the issue_comment works from the refs/main branch by default, and doesn't bring the PR context anyhow. Since i was testing it from the default branch in paritytech-stg - it was working fine, but from real PR non-default branch it didn't push result to PR branch.