decathlon / pull-request-labeler-action Goto Github PK

The labelling action is configured for my workflow, and it is working perfectly fine for almost 2 and a half months, but it is causing trouble. The problem is here it is not triggering for some pull requests, and it get resolved automatically after sometime. There is no pattern as it is happening for random pull request's, i need to quickly act upon this as this was a required status check in my workflow.Please help me out in this case :)

1. Create a PR who add a label automatically
2. Re-push modifications on this PR

If the first push already add a label, Action remove it and add it again.

Behavior expected: Check if the Action already exist and remove it only if it is necessary.

Hi there!
I added labeler, but it crashes with a following error:

✖  fatal     HttpError: Resource not accessible by integration 
    at response.text.then.message (/app/node_modules/@octokit/request/dist-node/index.js:66:23)
    at process._tickCallback (internal/process/next_tick.js:68:7)

workflow run: https://github.com/OpenDiablo2/OpenDiablo2/pull/1120/checks?check_run_id=2435495674
workflow file: https://github.com/OpenDiablo2/OpenDiablo2/blob/eb470533c42e2595f409b0b98caf020b4d361d43/.github/workflows/labeler.yaml

I suppose, that this happens if someone without merge access opens the pull request.

We need to find a way to cover code being processed in entrypoint.ts by mocking action-toolkit operations

Labels are only applied based on to first page of listed files under PR. See: https://developer.github.com/v3/#pagination

Hello,
In order to fix a bug on the wiki page creator action, I switch the version to the latest docker image.

uses: docker://decathlon/wiki-page-creator-action:latest

Once we have created a 2.0.0 of this docker image, we should fix the version.
Regards,
Alexandre.

Hi :)

This is a great tool that I want to use in an Open Source environment.
My only issue is that I cannot figure out how to exclude a path from getting a label... Is this possible?

Kind regards,

Is there any way to enable this pr label by action to support others events like pull_request.assigned ?

Why is this failing? Can you exclude pebcak on my end?

ℹ  info      Open sourced by
...
ℹ  info      Running Action
ℹ  info       Configured filters:  [ { regExp: '.*\\.rs+$', labels: [ 'rustlang' ] },
  { regExp: '.*\\.py+$', labels: [ 'python' ] },
  { regExp: '.*\\.c+$', labels: [ 'c-lang' ] },
  { regExp: '.*\\.cpp+$', labels: [ 'CPP' ] },
  { regExp: '.*\\.sh+$', labels: [ 'shell' ] },
  { regExp: '.*\\.bash+$', labels: [ 'bash' ] },
  { regExp: '.*\\.br+$', labels: [ 'brainfuck' ] },
  { regExp: '^(.*\\Cargo.toml)$', labels: [ 'dependencies' ] } ]
ℹ  info      Checking files list for PR#37
ℹ  info      Listing files (page: 1 | per_page: 100)...
ℹ  info      Loaded 2 files
ℹ  info      Checking files... [ 'ping', 'src/bin/main.py' ]
ℹ  info      Labels to remove:  []
ℹ  info      Labels to add:  [ 'python' ]
✖  fatal     HttpError: Resource not accessible by integration 
    at response.text.then.message (/app/node_modules/@octokit/request/dist-node/index.js:66:23)
    at process._tickCallback (internal/process/next_tick.js:68:7)
##[error]Docker run failed with exit code 1

Affected run: https://github.com/RXT0112/Zernit/pull/37/checks?check_run_id=427509002

Scenario:

1. Opening a new Pull request with documentation and tests files

• Before: No Labels
• After: ["documentation", "tests"]

2. Adding a new label (manually - which is not configured): ["documentation", "tests", "manual-label"]
3. Pushing once more but removing the documentation files from the pull request changes, I should have: ["tests", "manual-label"]

So I should only remove ["documentation"] in this case

In the same way that labels are automatically attached, would it be possible to also automatically request reviewers as well based on file regex?

The use case is pretty similar as with labels, but it would be extra helpful to be able to tag the specific domain expert, like

*.sql -> request review from DBA
*.js -> request review from front-end guy

etc.

I want to use this action to automatically label PRs for translations in my project.

The only - and for me most difficult - question I have is, what pattern I would need to use in order to only apply the label when the PR is towards those translations.
The translations always go towards json files located under src/resources/lang, the src/resources folder however also contains other json files for configuration settings and similar, so this should be ignored.

I'm not a pro at regex so Idk what would be a good pattern to cover the above requirements/rules.

Breaking changes as most of the used functions are deprecated and we also need to challenge if actions-toolkit is still relevant.
References:

• https://octokit.github.io/rest.js/
• https://www.npmjs.com/package/@octokit/rest

Hi, i just tried to set up the PR label action, this is how i configured it, following the documentation at
https://github.com/marketplace/actions/pr-label-by-files

This is my configuration file

The problem is that the github test fails, outputting this error about Docker installation

Complete log at https://pipelines.actions.githubusercontent.com/LzYT1jTHIIqkUqIVejfHz5PKS0a4Ln9lIjkGoSIu7hcrSGsXII/_apis/pipelines/1/runs/548/signedlogcontent/2?urlExpires=2021-10-11T09%3A36%3A41.9614721Z&urlSigningMethod=HMACV1&urlSignature=cx4nhAfNIpp5IrzPFGIlcoOdKwDOkVK1p7UMLEAVzbc%3D

Am i missing something about the configuration?

Github actions are still in Beta but version 2 provides some breaking changes we need to fix.
Few links here:

• New syntax for workflows (using YAML): https://help.github.com/en/articles/workflow-syntax-for-github-actions
• Migration from HCL to YAML: https://help.github.com/en/articles/migrating-github-actions-from-hcl-syntax-to-yaml-syntax
• Documentation mentioning the deadline of September 30st: https://developer.github.com/actions/
  

Is this project deprecated now that there is an official labeler from github actions ?