labeler
labeler copied to clipboard
actions
An action for automatically labelling pull requests
Closes #47, this refactors the existing logic to work with a `File` instead of just a filename (which for now just includes the filename and file status - `"added"`,`"modified"`, or...
#24 asked how to do this but #26 didn't really answer the question, despite adding many useful examples. Making some tests starting from the intuition in #10, I came up...
Our pull request template encourages users to link all pull requests to issues, which we spend quite some time labeling and triaging. So it would be great if this action...
This action so far has been based on using the file path(s) to determine which labels to set, but would it be possible to also have it support labels that...
name: "Pull Request Labeler" on: - pull_request_target jobs: triage: runs-on: ubuntu-latest steps: - uses: actions/labeler@main with: repo-token: "${{ secrets.GITHUB_TOKEN }}" '`- name: "Pull Request Labeler" on: - pull_request_target jobs: triage: ...
**Feature suggestion**: Using bots like dependabot or security advisory bots that automatically creates PRs with suggested fixes/updates, it would be nice to be able to ignore PRs from those users...
Configuration file for labeler can't be copied if you use shared workflow within the organization. Is there any way to put configuration inside the workflow?
I'm struggling to find the syntax to test a PR against a simple list of wildcard globs. I'd like to label a PR that touches any file that matches *.cpp,...
Similar to #25 I am getting the error "Could not get pull request number from context, exiting" I tried playing around with a variety of things but could not get...
I have auto-labeler set up on a monorepo and sometimes it generates (per configuration) more than 100 labels. However, it then fails with the error: ``` HttpError: Validation Failed. Issues...
