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.
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.