-
Notifications
You must be signed in to change notification settings - Fork 3
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
Allow companion branches to be conditionally customizable #32
Comments
This is if you want to modify the companion system to be used in non-companion use cases. Ultimately, we may want a separate workflow for the release process where the CI could make educated guesses based on our naming conventions and allow override as needed. Here is for instance how branches are named for a standard release:
it is important that we may need some flexibility on naming for emergency releases for instance. I think it would be fine to let the CI fail on the best guesses and have a way to tell the CI to switch the checks to another branch. |
@chevdor I was able to correlate However, the Cumulus one is more complicated since the suffixes don't match 1-to-1. Would it be possible to have the same |
Unfortuately no and it will not get better, one of the reason is that we will be splitting (it started on cumulus) runtime and client relesses so we may have different branches. Also the versions numbers are not in sync (on purpose) and will be more and more disconnected. |
For the use-case of paritytech/substrate#11276 where a PR is not targetting master, we can allow a syntax for specifying which branch should be used for the checks
Thus instead of
One would be able to say in the PR description
The text was updated successfully, but these errors were encountered: