-
Notifications
You must be signed in to change notification settings - Fork 329
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
Downstream tests assume release branch was cut #2508
Comments
This issue is stale because it has been open for 90 days with no |
/lifecycle frozen |
/good-first-issue |
@dprotaso: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
@dprotaso Can get the more context of this issue? |
Sure. We have a When a PR opens in this repo we run that change against other repos which consume This ensures we don't break anything - or find about a breaking change early on. We also have release branches along with our There's a window during our release process where we cut a branch in
In this scenario if the checkout fails - we should fallback and checkout the |
/assign |
This isn't always the case - #2291
The text was updated successfully, but these errors were encountered: