Run PR activities on push on non-default branch#248
Conversation
Coverage reportThe coverage rate went from
Diff Coverage details (click to unfold)coverage_comment/activity.py
coverage_comment/main.py
coverage_comment/settings.py
coverage_comment/github.py
|
kieferro
left a comment
There was a problem hiding this comment.
Great, looks good 👍. I still have a few small comments, but I tested with a copy of the template repo and everything seems to work fine.
487ac04 to
cdf71fa
Compare
|
Comments addressed. For the question of the default branch, I've:
|
cdf71fa to
ea13912
Compare
cb694a7 to
66ad832
Compare
|
I've also changed the |
kieferro
left a comment
There was a problem hiding this comment.
Looks great 👍
A decision regarding whether we need e2e tests for that or not
I'm not quite sure if this is so easy to test if we also want to test the normal use cases and therefore want to keep pull_request as a trigger. We could build some system that this trigger is ignored for example if the PR title contains a certain word and we create a PR which contains that word and tests if it also works only through the push trigger, but I don't know if that's worth the effort. What's your assessment?
I agree with you :) |
Closes #234, Closes #246
Still needs:
But the code is written, and we already have 100% coverage so that's a good start.