fix: fix updating comments in lockfile-changes workflow #933
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gmaclennan
force-pushed
the
fix/lockfile-changes-workflow
branch
from
c7003ac
to
99853a2
Compare
gmaclennan
force-pushed
the
fix/lockfile-changes-workflow
branch
from
f5c9f12
to
99853a2
Compare
EvanHahn
approved these changes
Oct 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This fixes the updating of comments by the lockfile-changes workflow. It requires a patch to the action, so we are now using our fork: digidem/npm-lockfile-changes#1
A small thing, but it's been frustrating me getting all comments on the PR from this bot. The issue was happening because we are using a custom github app token to run the action.