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

Autocategorize by label? #35

Closed
derberg opened this issue Aug 2, 2018 · 6 comments · Fixed by #85
Closed

Autocategorize by label? #35

derberg opened this issue Aug 2, 2018 · 6 comments · Fixed by #85

Comments

@derberg
Copy link

derberg commented Aug 2, 2018

Hey, did you think about taking this bot a step forward in the future and make it configurable that the drafter only lists merged PR with specific label, and even that you can have different sections in a template and Pr with specific label in the section?

@toolmantim
Copy link
Collaborator

Hey @derberg! Absolutely. Different PR labels for different sections is super high on my wish list.

@salmanulfarzy
Copy link
Contributor

Tried to modify messages for releases. But, setting up local environment with probot of forks got me for hours.

@toolmantim
Copy link
Collaborator

Sorry to hear @salmanulfarzy! What were you trying to modify them from/to?

@salmanulfarzy
Copy link
Contributor

I was trying to change the release note into (#pr) message - @author format and extending them to be used with template variable, to support user customization.

@toolmantim
Copy link
Collaborator

toolmantim commented Aug 8, 2018

@salmanulfarzy I could look at adding that for you. Perhaps a “change-template” config, that took $number, $title and $author template variables?

Let’s open it as a new issue tho, as I think it’s unrelated to the original issue.

@toolmantim toolmantim changed the title future enhancements Autocategorize by label? Aug 8, 2018
@salmanulfarzy
Copy link
Contributor

Perhaps a “change-template” config, that took $number, $title and $author template variables?

That sounds great 😄

open it as a new issue tho, as I think it’s unrelated to the original issue.

Sure, I'll open up a new issue. Mentioned it here because may be it could be considered on enhancements.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants