Fix using head_pipeline instead of pipeline in GitLab
#289
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
- Due to [GitLab docs](https://docs.gitlab.com/ee/api/merge_requests.html) we should prefer using head_pipeline instead of pipeline as it contains more information
Vacxe
approved these changes
Oct 23, 2024
- Fix Gitlab pipeline status test
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.
Due to GitLab docs we should prefer using
head_pipelineinstead ofpipelineas it contains more information.Additional to that, sometimes I caught crashes on danger-kotlin when
pipelinestatus was incorrect in that field or even whenpipelinefield wasnull.But I can't just mark
pipelinefield as nullable, cause it will cause backward incompatibility.