feat: implement CI pipeline status reporting when evaluating MR #17
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.
Breaking change:
--commit
/$CI_COMMIT_SHA
variablescm-engine evaluate
now requires--commit
(or envCI_COMMIT_SHA
) to work.The
CI_COMMIT_SHA
variable is provided in GitLab CI pipelines automatically; so hopefully shouldn't break anything.--update-pipeline
/$SCM_ENGINE_UPDATE_PIPELINE
(default:true
)Projects without CI pipelines might fail due to lack of CI pipeline API; other projects should now see an external CI pipeline status from
scm-engine
showing success/failure + relevant error message whenscm-engine
is processing an MR