-
Notifications
You must be signed in to change notification settings - Fork 33
NETOBSERV-229 create pre-merge image on PR via action #173
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
Conversation
Uses the 'ok-to-test' label to trigger the build/push
Codecov Report
@@ Coverage Diff @@
## main #173 +/- ##
=======================================
Coverage 58.20% 58.20%
=======================================
Files 55 55
Lines 3137 3137
=======================================
Hits 1826 1826
Misses 1190 1190
Partials 121 121
Flags with carried forward coverage won't be shown. Click here to find out more. Continue to review full report at Codecov.
|
| github.rest.issues.createComment({ | ||
| issue_number: context.issue.number, | ||
| owner: context.repo.owner, | ||
| repo: context.repo.repo, | ||
| body: 'New image: ${{ steps.push-to-quay.outputs.registry-paths }}. It will expire after two weeks.' | ||
| }) |
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.
I'm a bit confused. If this workflow is triggered by a PR, then what is the issue in context where the comment is created?
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.
in github API, a PR is apparently some special kind of issue. But the comment is actually created on the PR
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.
@jotak looks good to me
|
thanks |
Uses the 'ok-to-test' label to trigger the build/push