The task that runs when a new issue is opened, issue-labler, is powered by an Action that's three years out of date & relies on Node v12. GitHub Actions no longer supports Node v12, forces the Action to run on v16.
The actual error that is causing the task to fail though is attempting an HTTP DELETE on https://api.github.com/repos/dendronhq/dendron/issues/3950/labels/scope.schema which returns HTTP 404 where #3950 was the issue I created, and it never had the scope.schema tag, nor should it have had.
All this code does is upgrade the version of issue-labler & changes how the GitHub token is accessed to match the documentation. My hopes are that the new plugin will handle deleting a non-existent tag more gracefully. (That & not want to run on Node v12.)
I can't really test this without deploying it. In fact it has to be in master for the issue-labler to run, so I should set this up on a separate repo & see if it works…
Pull Request Checklist
First Time Specifics
[X] if its your first pull request to Dendron, watch out for the CLA bot that will ask you to agree to Dendron's CLA
[X] if its your first pull request and you're on our Discord, add your discord handle so that we can award you the horticulturalist role when the PR is merged
I'm @dysbulic.
Commit
[X] make sure your branch names adhere to our branch style
[ ] make sure the commit message follows Dendron's commit style
[X] if this pull request is addressing an existing issue, make sure to link this PR to the issue that it is resolving.
[ ] if your change reflects documentation changes, also submit a PR to dendron-site and mention the doc PR link in your current PR (NOTE: submit the PR against the dev branch of the dendron-site repo)
[ ] does this change introduce a new or better way of doing things that others need to be aware of? if so, an async should be created and a process added in Development or Packages
The task that runs when a new issue is opened,
issue-labler
, is powered by an Action that's three years out of date & relies on Node v12. GitHub Actions no longer supports Node v12, forces the Action to run on v16.The actual error that is causing the task to fail though is attempting an HTTP
DELETE
onhttps://api.github.com/repos/dendronhq/dendron/issues/3950/labels/scope.schema
which returns HTTP 404 where #3950 was the issue I created, and it never had thescope.schema
tag, nor should it have had.All this code does is upgrade the version of
issue-labler
& changes how the GitHub token is accessed to match the documentation. My hopes are that the new plugin will handle deleting a non-existent tag more gracefully. (That & not want to run on Node v12.)I can't really test this without deploying it. In fact it has to be in
master
for theissue-labler
to run, so I should set this up on a separate repo & see if it works…Pull Request Checklist
First Time Specifics
I'm @dysbulic.
Commit
Code
Tests
Docs
[ ] if your change reflects documentation changes, also submit a PR to dendron-site and mention the doc PR link in your current PR (NOTE: submit the PR against the
dev
branch of the dendron-site repo)[ ] does this change introduce a new or better way of doing things that others need to be aware of? if so, an async should be created and a process added in Development or Packages