-
Notifications
You must be signed in to change notification settings - Fork 74
Add "improvement" type as suggested by the spec #13
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
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! I don't like how lengthy this type is, but it is effective spec now, so we should include it.
Thanks! Appreciate the quick turn around. Think we can get a version bump? We'd like to include these changes in the Github semantic pull request bot: |
@binarylogic I've now published to |
@AndersDJohnson Would you also be willing to cut a GitHub |
@matthewfeickert Sure, I just pushed the tag for Note that historically we've pushed tags here but not necessarily created GitHub releases out of them. Will that be a problem for your tooling? |
Thanks very much! I appreciate you being so responsive.
Good question. I'm not actually sure, as I just gave a cursory glance and noticed that this PR was quite recent when I was reporting my issue to the Though at this point as you've been so helpful I think that any discussion on this PR can stop and that any follow up can just be on the Issue I made. Thanks again! :) |
@binarylogic @matthewfeickert It looks like they removed I'm proposing we consider removing it in #16, so I would appreciate if you could share thoughts there. |
👍 Go for it. I don't have strong opinions. We're able to customize our PR check to allow for custom types. |
@AndersDJohnson Thanks very much for the heads up. This all sounds fine to me, so I'll adjust things on the pyhf side accordingly. |
From the spec: