-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: add repo status failure call if commits fail quailty checks #114
fix: add repo status failure call if commits fail quailty checks #114
Conversation
Signed-off-by: Paul Horton <phorton@sonatype.com>
Signed-off-by: Paul Horton <phorton@sonatype.com>
@@ -366,6 +368,11 @@ func EvaluatePullRequest(logger *zap.Logger, postgres db.IClaDB, evalInfo *types | |||
return err | |||
} | |||
|
|||
err = createRepoStatus(client.Repositories, evalInfo.RepoOwner, evalInfo.RepoName, evalInfo.Sha, "failure", "One or more commits haven't met our Quality requirements.", botName) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm looking into trying to use the Mock objects to see if we can assert some state in unit tests for these sorts of things. It might complicate this PR a little, but should hopefully open the door to better unit tests and maybe allow refactoring some of these huge methods into smaller units. Spoiler: repositoriesMock
yadda, yadda...
…mocks update mocks to assert multiple calls to mock functions
Quality Gate passedIssues Measures |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1
Resolves #113