Updating image-labler
GitHub Action
#3952
Draft
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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