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
Right now, a single matcher is supported for items like the title or the body like explained in the documentation:
labelers:
# The label to be applied.
#
- label: 'issue'
# Matches the text of the first commit line.
# Value may be plain text or regex.
# Use `regex:` as prefix to indicate a regex.
#
title: 'regex:fix:'
# Matches the full text of the commit.
# Value may be plain text or regex.
# Use `regex:` as prefix to indicate a regex.
#
body: 'Fixes #'
it would be quite handy to additionally support a list of matchers like that:
where if any of the matchers matches, the label will be applied. Additionally, support adding a flag after the second colon to be able to express insensitive pattern. This would be similar to the javascript notation of e.g. '/bump:/i'.
The notation for the flag might not work in a backwards compatible way, but having the possibility to express case-insensitive pattern in an easy way would be certainly useful imho.
The text was updated successfully, but these errors were encountered:
As a workaround you could use regex:deps|dependencies|bump.
Migrating the title property from scalar to list/array is a non-compatible change which should be made in v2 IMHO.
Right now, a single matcher is supported for items like the title or the body like explained in the documentation:
it would be quite handy to additionally support a list of matchers like that:
where if any of the matchers matches, the label will be applied. Additionally, support adding a flag after the second colon to be able to express insensitive pattern. This would be similar to the javascript notation of e.g. '/bump:/i'.
The notation for the flag might not work in a backwards compatible way, but having the possibility to express case-insensitive pattern in an easy way would be certainly useful imho.
The text was updated successfully, but these errors were encountered: