derberg/NPM Dependency Manager For Your GitHub Organization
This action handles automated update of dependencies in package.json between projects from the same GitHub organization.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| custom_id | This custom_id is added as a unique identifier value to the PR created by the bot so the bot can later recognize it as created by the bot, so it updates existing PR instead creating new one. If custom_id is not specified, action assumes that you still want bot to create multiple PRs in one repo, with multiple updates. Once you add the custom_id, you enable flow with active one PR per repo. | no | — |
| github_token | Token to use GitHub API. It must have "repo" scopes so it can push to repos. It cannot be the default GitHub Actions token GITHUB_TOKEN. GitHub Action token's permissions are limited to the repository that contains your workflows. Provide token of the user that has rights to push to the repos that this action is suppose to update. | yes | — |
| committer_username | The username (not display name) of the committer that will be used in the commit of changes in the workflow file in specific repository. In the format `web-flow`. | no | web-flow |
| committer_email | The email of the committer that will be used in the commit of changes in the workflow file in specific repository. In the format `noreply@github.com`. | no | noreply@github.com |
| commit_message_prod | It is used as a commit message when bumping dependency from "dependencies" section in package.json. In case dependency is located in both dependencies and devDependencies of dependant, then prod commit message is used. It is also used as a title of the pull request that is created by this action. | no | — |
| commit_message_dev | It is used as a commit message when bumping dependency from "devDependencies" section in package.json. It is also used as a title of the pull request that is created by this action. | no | — |
| packagejson_path | Paths to package.json file if not located in the root of the project. Provide just the paths without file name. In the format: `./nested/location` or as a comma-separated list for multiple paths `./path1,./path2`. | no | ./ |
| repos_to_ignore | Comma-separated list of repositories that should not get updates from this action. Action already ignores the repo in which the action is triggered so you do not need to add it explicitly. In the format: `repo1,repo2`. | no | — |
| base_branch | Name of the base branch, where changes in package.json must be applied. It is used in PR creation. If not provided, default branch is used In the format: `next-major`. | no | — |
| search | Whether to search for multiple package.json files in the repository. Useful for monorepos. Note: Enabling `search` overrides the list of paths provided. | no | false |
| ignore_paths | Comma-separated list of paths/directories that should be ignored when searching for package.json files. Only used if search input is set to true. In the format: `./path/to/ignore,./another/path/to/ignore`. | no | — |
Outputs
no outputs