-
Notifications
You must be signed in to change notification settings - Fork 23
docs: remove default_branch from config.yaml
#1809
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
base: stackhpc/2025.1
Are you sure you want to change the base?
Conversation
By setting the `default_branch` the generation of release notes fails to capture all of the tags releases within a given branch.
|
This was required to get zuul CI to work #1791 Do you know any other way we could get this to work? |
What is Zuul doing that means the configuration for release notes requires default branch set? |
It runs a pep8 job which isn't really pep8, it's more just a release notes check. For some reason it succeeds in GH CI but fails in zuul https://zuul.stackhpc.com/t/stackhpc/build/54c03714f1f2432ea7db98c1900e641b |
It is because the repository is cloned with The docs for reno say that |
By setting the
default_branchthe generation of release notes fails to capture all of the tags releases within a given branch.