Clean up the npm hardening action and document disabled schedules - #5
Merged
Merged
Conversation
- verify-npm-hardening: 2-space indentation like the other files; the parsed YAML is unchanged. The usage header now shows a SHA-pinned reference and points to security.yml - Guide: GitHub disables scheduled workflows in public repositories after 60 days without activity
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
No behaviour change.
verify-npm-hardening: 2-space indentation, like every other workflow and action here. The parsed YAML is identical before and after. The usage header showed an old v4 checkout SHA and a local path; it now shows a SHA-pinned reference and points tosecurity.yml.