You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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!
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!
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.
The text was updated successfully, but these errors were encountered: