-
Notifications
You must be signed in to change notification settings - Fork 72
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
Next minor release v1.1.0 #97
Comments
+1. |
[optional] support for pull requests #109 |
should resolve #110 too |
would love to have this resolved #143 |
Shall we try to set a timeline for this release, to avoid delaying further? Let's discuss in our next meeting. I think toe original blocker was around token for branch protection, but there seems to be some agreement that we should allow tokens and document which checks will be available depending on token type (GITHUB_TOKEN, PAT scopes, etc) |
Let me try to do that for mi April |
Having debug messages in the output for troubleshooting would be useful. It's been an ask from time to time. I don't think we can do that for this release, but for the next one when we switch to golang library we should be able to do it. |
/cc @naveensrinivasan let us know when some of the e2e tests are done. I'll start working on the documentation myself |
@laurentsimon Tests are done, and everything looks good. #180 (comment) |
Great, Feel free to close the 2 issues related to e2e test listed in the first description |
Looks like we have all TODOs done for this release |
Closing this since looks like this is done. Please re-open if needed. |
End-to-end tests for workflow_dispatch #179Using this action getting error #154${{ github.token }}
instead of PAT #78BUG: Failures in Branch-Protection during release testing scorecard#1320non blocking so skippingFeature: better remediation steps scorecard#1850 (comment)First iteration of the issue completedThe text was updated successfully, but these errors were encountered: