Added "continue-on-error: true" to step which posts coverage comment #883
Conversation
This file contains hidden or 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
liudmylaru
requested review from
darenr,
mayoor,
mrDzurb,
VipulMascarenhas and
qiuosier
as code owners
oracle-contributor-agreement
bot
added
the
OCA Verified
darenr
approved these changes
Jun 14, 2024
VipulMascarenhas
approved these changes
Jun 14, 2024
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.
Description
With recent PR from user, who is not in special write-permission-group, there was an error in one step of our test pipeline observed. That step showed 403 erorr (https://github.com/oracle/accelerated-data-science/actions/runs/9504255692/job/26199643545?pr=869) on sending POST to add comment into respective PR. Even though GH action has permissions set to write for pull-request, user should be able to have permission to write to repo (be in that special group).
To overcome this and future issues with PR from such users I am suggesting to make a step, which adds comment to PR optional (add continue-on-error: true). We still will have our coverage reports generated and published to artifacts and PR reviewers can see coverage downloading from artifacts generated by GH actions, but this will omit such message in PR:
