-
Notifications
You must be signed in to change notification settings - Fork 224
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
issue labeler workflow failing #3884
Comments
#3885 opened for this. |
Nope. I didn't add perms to the needed job in the labeler workflow. |
That didn't work. Or at least likely didn't work. I just got another failure:
|
The labeler workflow is always failing now: https://github.com/elastic/apm-agent-nodejs/actions/workflows/labeler.yml |
Nope. That didn't work. https://github.com/elastic/apm-agent-nodejs/actions/runs/8210315149/job/22457519729
Lovely. That
and I added the former for those two: apm-agent-nodejs/.github/workflows/labeler.yml Lines 10 to 14 in 7a697bc
based on what I saw in the .NET agent here: I assume my comment isn't impactful. This one is getting frustrating. |
This is based on the more-recently updated labeler.yml in the apm-agent-dotnet repo. - Switch away from Alex's old unmaintained issue-labeler action. - Remove old debugging "Show team membership" step. - Stop assigning the issue to project 454 (and old GH proj we no longer use) - The hope is that these changes will also close #3884.
This is based on the more-recently updated labeler.yml in the apm-agent-dotnet repo. - Switch away from Alex's old unmaintained issue-labeler action. - Remove old debugging "Show team membership" step. - Stop assigning the issue to project 454 (and old GH proj we no longer use) - The hope is that these changes will also close #3884.
And it continues... The labeler workflow is now failing with:
e.g.: https://github.com/elastic/apm-agent-nodejs/actions/runs/8325325014 nextNext attempt will be to switch to the technique(s) being used in apm-agent-java which Riccardo (internal Slack comment: https://elastic.slack.com/archives/C9A6ANR5Y/p1710418037227959) confirmed is "the way" now. |
- use more reliable 'elastic' org membership test for triage, etc. labels - bypass 'action-add-labels' action to avoid another dep - drop agent-nodejs label that we no longer require for use in GH projects Fixes: #3884
5th time's the charm. |
Earlier failed attempts were elastic#3885 and elastic#3886. Fixes: elastic#3884
This is based on the more-recently updated labeler.yml in the apm-agent-dotnet repo. - Switch away from Alex's old unmaintained issue-labeler action. - Remove old debugging "Show team membership" step. - Stop assigning the issue to project 454 (and old GH proj we no longer use) - The hope is that these changes will also close elastic#3884.
- use more reliable 'elastic' org membership test for triage, etc. labels - bypass 'action-add-labels' action to avoid another dep - drop agent-nodejs label that we no longer require for use in GH projects Fixes: elastic#3884
latest dependabot PRs are failing in the issue labeler CI workflow and blocking the merge. The POST request failed with a 403 so we should start by checking if the token has expired or was rotated
Ref: https://github.com/elastic/apm-agent-nodejs/actions/runs/8042141883/job/21962393814?pr=3883
excerpt of the error
The text was updated successfully, but these errors were encountered: