enhance(api/webhook): update hook status to skipped when build is skipped #993
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
claire1618
previously approved these changes
Oct 26, 2023
timhuynh94
previously approved these changes
Oct 26, 2023
|
Looks like test failed! |
Codecov Report
@@ Coverage Diff @@
## main #993 +/- ##
=======================================
Coverage 70.36% 70.36%
=======================================
Files 315 315
Lines 13199 13199
=======================================
Hits 9288 9288
Misses 3444 3444
Partials 467 467
|
timhuynh94
previously approved these changes
Oct 26, 2023
wass3r
reviewed
Oct 26, 2023
wass3r
approved these changes
Oct 26, 2023
claire1618
approved these changes
Oct 27, 2023
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.
Oftentimes, users will have their pipeline steps purged completely, and the hook's successful status in addition to the lack of any messaging leads to confusion. End result of these changes would be something like this:
The above provides a clear path forward for users.