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
release-drafter doesn't have extensive enough configuration support. Optimally, PRs from Renovate updating application dependencies would automatically be labeled according to Renovate's current configuration, but currently, the autolabeler adds additional labels. We could ignore branches starting with renovate/ but that's not the cleanest solution imo. Currently, Renovate sets labels on its PRs, only because this behavior could not be mimicked with release-drafter. With actions/labeler we'd be able to have 1, and only 1, location to configure automatic PR labels.
What
PRs from Renovate/with the title starting with chore(deps) updating GitHub Actions should get the labels "kind:chore" and "semver:none". PRs from Renovate/with the title starting with chore(deps) updating everything else should get the labels "kind:dependencies" and "semver:patch".
The text was updated successfully, but these errors were encountered:
Why
release-drafter doesn't have extensive enough configuration support. Optimally, PRs from Renovate updating application dependencies would automatically be labeled according to Renovate's current configuration, but currently, the autolabeler adds additional labels. We could ignore branches starting with
renovate/
but that's not the cleanest solution imo. Currently, Renovate sets labels on its PRs, only because this behavior could not be mimicked with release-drafter. With actions/labeler we'd be able to have 1, and only 1, location to configure automatic PR labels.What
PRs from Renovate/with the title starting with chore(deps) updating GitHub Actions should get the labels "kind:chore" and "semver:none". PRs from Renovate/with the title starting with chore(deps) updating everything else should get the labels "kind:dependencies" and "semver:patch".
The text was updated successfully, but these errors were encountered: