cli: log when the server registered a GitHub check (TB-377) - #37
Merged
Conversation
…(TB-377)
The run endpoint now returns ci_check { provider, repo, commit_sha } when
the CI metadata matched an installed TestingBot GitHub App. Surface it so
users see the PR status will update, and know why it did not when the
line is absent.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Companion to the web change for TB-377 (GitHub PR checks for Maestro runs, web branch
feat/TB-377-maestro-pr-checks). The run endpoint returnsci_check { provider, repo, commit_sha }when the run's CI metadata matched an installed TestingBot GitHub App; the CLI logs one line so users know the PR status will update. No behaviour change otherwise.Test plan