bpmn-visualization-js
bpmn-visualization-js copied to clipboard
ci: add labels automatically on PR creation or update
- Add step on workflow of metadata PR checking, to add labels
- Add labeler config
I'm not currently convinced about using this automation. It's going to be difficult to maintain, the files are sometimes modified for purposes other than what is configured and so we'll have to delete the tags in some cases, which will represent additional maintenance. It also adds to the load on GH Actions.
Isn't it possible to configure only the branch name? That would simplify maintenance. We should also probably review our Contributing guide as the recommended branch name doesn't follow the patterns proposed in the labeler configuration.
I've known about the labeler action for a while and haven't seen a project where it was useful on PR. Do you have any examples to share where you've seen value in adding such automation?
Can we discuss this in person?
ℹ️ We have recently change our convention for the branch name #3263 It now matches the branch patterns defined in the workflow proposed here.
As discussed with @tbouffard, we decided to close this PR as we don't know exactly who is working on this project and if it was useful for them.
Don't hesitate to reopen it if you need to 😉.