Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/bencooper222/check-for-node-dep-changes
GitHub action to check if dependencies have been changed for node project
https://github.com/bencooper222/check-for-node-dep-changes
Last synced: 15 days ago
JSON representation
GitHub action to check if dependencies have been changed for node project
- Host: GitHub
- URL: https://github.com/bencooper222/check-for-node-dep-changes
- Owner: bencooper222
- License: mit
- Created: 2019-04-23T20:39:13.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2022-01-22T04:35:49.000Z (almost 3 years ago)
- Last Synced: 2024-08-01T16:34:41.099Z (3 months ago)
- Language: JavaScript
- Homepage:
- Size: 25.4 KB
- Stars: 0
- Watchers: 2
- Forks: 1
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
- License: LICENSE.MD
Awesome Lists containing this project
README
# check-for-node-dep-changes
This is a GitHub action for Node projects to check if the dependencies have changed since the last commit on the current branch.
I've tested it on most of my projects and I'm pretty convinced that it's reliable but pretty != 100%. As of right now, I would only rely on this project to do reversible things that don't affect production. Do note that GitHub Actions itself is in beta and is not 100% reliable - I've dealt with its quirks several times.
That said, if you're comfortable with those caveats, this action is pretty simple:
```javascript
action "detect dependency changes" {
uses = "bencooper222/check-for-node-dep-changes@master"
secrets = ["GITHUB_TOKEN"]
}
```
If dependencies have changed (both normal and dev), any actions that `uses` this action will proceed. Otherwise, that chain of actions will end.