Skip to content
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

Refuse release dependent on bug number #916

Open
sils opened this issue Aug 10, 2015 · 11 comments
Open

Refuse release dependent on bug number #916

sils opened this issue Aug 10, 2015 · 11 comments
Labels

Comments

@sils
Copy link
Contributor

sils commented Aug 10, 2015

It would be nice to be able to be able to configure rultor like this:

release:
  requirements:
    bugs:
      label: bug
      max: 0

to let rultor use the github API to check if there are more than "0" bugs labelled with "bug" and refuse the release if there are any bugs that would actually be released.

@alex-palevsky
Copy link
Contributor

@yegor256 dispatch this issue please

@yegor256
Copy link
Owner

@sils1297 good idea, but I would rather make the configuration simpler, for example:

release:
  required:
    label-absent: bug
    arg-matches: tag [0-9\.]+
    label-max: minor-bug

What do you think?

@original-brownbear
Copy link
Contributor

@sils1297 still interested in this ? :)

@sils
Copy link
Contributor Author

sils commented Feb 22, 2016

Would be neat. We're unable to use rultor for releases though since we always need two version numbers (the one of the release and the one after as we're doing development releases). Thus we wouldn't use this feature indeed with our current setup.

@original-brownbear
Copy link
Contributor

@sils1297 thanks, lets not dismiss it then but prioritize it realistically :)

@original-brownbear
Copy link
Contributor

@alex-palevsky valid bug.

@original-brownbear
Copy link
Contributor

@alex-palevsky this is postponed.

@alex-palevsky
Copy link
Contributor

@alex-palevsky valid bug.

@original-brownbear added "bug" tag to this issue

@alex-palevsky
Copy link
Contributor

@sils1297 I set the milestone to 2.0 since there is nothing set yet

@alex-palevsky alex-palevsky added this to the 2.0 milestone Feb 24, 2016
@alex-palevsky
Copy link
Contributor

@alex-palevsky this is postponed.

@original-brownbear sure, thanks, I added "postponed" label to it

@alex-palevsky
Copy link
Contributor

@alex-palevsky this is postponed.

@original-brownbear I will assign somebody else to this issue

@yegor256 yegor256 removed this from the 2.0 milestone Nov 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants