Closed botchris closed 3 years ago
Heya @ChristopherCastro, thanks for reporting this issue. Firstly can you check to see if the issue is replicated when using our version of this action which has been updated and is currently undergoing maintenance. #24
# super Labeler
- name: Super Labeller
uses: Videndum/super-labeler-action@1.0.1
with:
GITHUB_TOKEN: '${{ secrets.BOT_TOKEN }}'
If you are still receiving this issue, please do the following:
ACTIONS_STEP_DEBUG
with the data true
Copying the action logs doesn't reveal any secrets
or confidential data - at most it may reveal the labels you are using. You are welcome to take a look through our debugging logs here if you want to see what sort of data is output.
Please feel free to open a ticket on https://github.com/Videndum/super-labeler-action and I can support you there with the latest version of this action.
@ChristopherCastro I can confirm that this bug does not exist within the version maintained here: #24
This is due to the issue discussed in #18 which has been implemented for a while on the maintained repository.
If you are unsure still, here is confirmation from our debugging logs https://github.com/Videndum/super-labeler-action/runs/1388853315?check_suite_focus=true#step:3:33
// CLOSE ISSUE PLEASE
Oh, I see.
I can confirm that using Videndum/super-labeler-action@1.1.0
works pretty well when having more than 30 labels. However, suggested v.1.0.1 always fails for me with the error message "Cannot read property 'charAt' of undefined"
Describe the bug
seems like it tries to incorrectly create a label which already exists, it shows the following message:
It looks like it only see the first 30 labels from the repo.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
It should not create an existing label
Config Add your
labels.json
config and Github Actions workflow:Github Actions Output
private repo, cant provide due confidential issues.