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
Fix typos #1616
Fix typos #1616
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
@atugushev That requirement to prevent merges on branches that are not updated does really impede making a new release as any other merge invalidates the previous runs. |
Yeah, this is kinda annoying. Feel free to ask @jazzband/roadies on the issue tracker to disable that requirement. See also #1085 |
I posed on #jazzband channel on matrix, but I am not sure is the key people are there. |
@atugushev The feature is benefic in general as I know that some changes can easily break the master but maintainers should be able to bypass it. It should act more like a warning than a hard requirement. |
🥳 🥳 🥳 🥳 🥳 |
Contributor checklist
Maintainer checklist
backwards incompatible
,feature
,enhancement
,deprecation
,bug
,dependency
,docs
orskip-changelog
as they determine changelog listing.