fuxingloh / multi-labeler Goto Github PK

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Pending Approval

These branches will be created by Renovate only once you click their checkbox below.

• bump(deps): update dependency minimatch to v10
• bump(deps): update peter-evans/create-pull-request action to v7
• 🔐 Create all pending approval PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• bump(deps): update actions/setup-node action to v4.0.4
• bump(deps): update dependency @vercel/ncc to ^0.38.2
• bump(deps): update actions/checkout action to v4.2.0
• Click on this checkbox to rebase all open PRs at once

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Hi there.
Just started using this action so if I'm doing something silly please let me know but I can't seem to get valid parenthesis-related regex statements working in my labeler.yml.

PR title is: "build(deps): apply minor and patch dependency updates test" - we use both "^build(deps): ." and "^build(dev-deps): ." commit and PR title tags and I'd like to catch both and apply a "dependencies" label.

The following labeler.yml catches that PR title and succesfully applies the label:

version: v1

labels:
  - label: "dependencies"
    sync: true
    matcher:
      title: "^build.*"
      commits: "^build.*"

However, to use parentheses I am obviously going to have to escape them. \( isn't valid YAML so I went for \x28 instead and came up with the following valid regex:

title: "^build\x28(deps|deps-dev)\x29: .*"

However, the action then does nothing - officially passed but gives no useful logging output and doesn't apply the label.

Is there a debug flag for getting useful logging? And should valid regex like this work?

Any help much appreciated.

to create label based on the path of the changed files

for example: files changed under proj/test-proj-1
the label should be test-proj-1

here is an action with this feature

https://github.com/TinkurLab/monorepo-pr-labeler-action/blob/master/app.js

Thanks for the great tool!

Could you document more on the files.all option and output option?

Both of them are not very clear from the test case.

Here is what I got.

1. output.labels as an array of labels. (This one is pretty simple)

2. files.all

it will match all glob expressions in the array. The behavior is like "and", while any is like "or".

Also it seems like the expression doesn't work correctly with !(xxx|zzz)/**

But it seems like it should work according to https://github.com/isaacs/minimatch

PS: if there is a way to pass the option of minimatch, that will be awesome!

There is some kind of error happening right after Label job,

Deploy preview failed
Error: The process '/usr/local/bin/npx' failed with exit code 1

It would be really great if there was an option to set case insensitivity.

At present you have to add /i to every line - I'm not sure if this might cause other issues but it's certainly a lot of repetition.

I like the super-fast labels-only approach of this action.

But, one of the things I was looking for is: label based on target branch (base branch) of pull request.

For example, I want to add a release label to PRs targeting release/* branches.

Is this something acceptable as a feature here?

Quite often we want to be sure that only one of a specific list of labels is present. Current options like any would indicate that it will pass even with 2+ matches, which could cause problems for changelog generation.

Runs for this action have started failing with:

Run fuxingloh/multi-labeler@v2

/home/runner/work/_actions/fuxingloh/multi-labeler/v2/webpack:/multi-labeler/lib/main.js:42
    throw new Error('Could not get issue_number from pull_request or issue from context');
^
Error: Could not get issue_number from pull_request or issue from context

and

Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: fuxingloh/multi-labeler@v2. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.

Looking at the action.yml here I can see:

runs:
  using: 'node16'
  main: 'dist/index.js'

Not being a node user, I'm unsure if this can just be updated to node20 and all will be well again.

Add ability to sync tags and remove tags that does not fit the condition provided inlabeler.yml?

Finally a labeler action that actually works on commit messages! We'll be having a lot of repositories using this action and would like to place the configuration in a central place (the @org/.github repo). How can I configure the action to use a configuration from a different repository?