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

Label PR based on base branch #54

Closed
hkdobrev opened this issue Mar 6, 2020 · 3 comments · Fixed by #203
Closed

Label PR based on base branch #54

hkdobrev opened this issue Mar 6, 2020 · 3 comments · Fixed by #203
Assignees
Labels
feature request New feature or request to improve the current logic

Comments

@hkdobrev
Copy link

hkdobrev commented Mar 6, 2020

Could the automatic labeler support more triggers than just the paths changed?

A very useful workflow for us would be set labels on the PR depending on the base branch of the PR. Depending on the Git branching workflow used in a project, this could have different use cases. For example, using the git-flow, a PR towards the development branch could be labeled as a feature and one towards master as a release.

If this feature request is implemented I imagine automatic labeling and its configuration could later be expanded to be based on branch patterns, author (if it's a robot for example) etc.

@XVilka
Copy link

XVilka commented Mar 11, 2020

Also related #55 - probably implementing these will share some code.

@MaksimZhukov MaksimZhukov added the feature request New feature or request to improve the current logic label Dec 12, 2022
@MaksimZhukov
Copy link
Contributor

Hello everyone!
We released the new alpha version of the action that includes the implementation of this feature. For more information, see the release notes. We would really appreciate it if you could try it out and provide us with your feedback.

I will keep this issue open until the stable version is released.
Thank you!

@MaksimZhukov MaksimZhukov self-assigned this Jul 11, 2023
@MaksimZhukov
Copy link
Contributor

Hello everyone!
We have released the new major version of the action that includes the implementation of this feature. Please read the action documentation to find out how to adapt your configuration files and workflows for use with the new action version.

Thank you all for your patience!
Do not hesitate to contact us if you have any questions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request to improve the current logic
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants