-
Notifications
You must be signed in to change notification settings - Fork 2
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
Feature: write status of the build/deployment as a PR comment when using github workflows #1115
base: main
Are you sure you want to change the base?
Conversation
☂️ Python Coverage
Overall Coverage
New FilesNo new covered files... Modified FilesNo covered modified files...
|
retention-days: 1 | ||
if-no-files-found: error | ||
|
||
pr-writeback: |
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.
Using a separate job because jq
is not installed in the toolkit container. And to install it need to install curl
first.
But jq
is pre-installed in the default runner image, so just went with that.
Ideally, I'd bake jq
into the toolkit docker image and then we could simplify the workflow a lot. No need to run a separate job, no need to upload/download log files. It'll be fast and simpler.
printf 'Toolkit dry run triggered: %s\n\n%s\n%s\n\n```\n%s\n```\n' \ | ||
"$RUN_LINK" "$B_STATUS" "$DR_STATUS" "$MSG" > pr-comment-body.txt | ||
|
||
gh pr comment $PR_NUMBER -F pr-comment-body.txt 2> pr-comment-error.log |
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.
this fails if comment body is too long, which also breaks the PR check
preliminary handling is implemented but needs more work and testing
Description
Updated the github workflow build template: write status of the build/deployment as a PR comment when using github workflows.
Checklist
_version.py and
pyproject.toml per semantic versioning.