loremlabs/Kudos for Code
Supporting your open source team...
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Dec 26, 2023
- License
- MIT
Pinned Snippet
uses: loremlabs/kudos-for-code-action@322d4a92a55a4247581a70ea94f48695c8f35785 # v1.0.9tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| destination | Where to save the generated kudos. Options: artifact, pool | yes | artifact |
| github-token | A GITHUB_TOKEN with custom permissions. | — | — |
| search-dir | Root directory containing package.json | yes | . |
| pool-id | PoolId to save kudos to at external pool service. | — | "" |
| identify-type | How should we identify Kudos? (sbom, setler) | — | sbom |
| identify-checks | Which methods should we use to identify the kudos? (kudos,contributors,lang) | — | kudos,contributors,lang |
| identify-langs | Which languages should we search for? (nodejs) | — | nodejs |
| setler-keys | Setler Kudos Keys | — | "" |
| pool-storage-token | Pool Storage Token | — | "" |
| pool-endpoint | Pool Endpoint | — | https://api.semicolons.com |
| skip-main-package | Don't create kudos for main package. | — | false |
| analyze-repo | Analyze the repo code and generate Kudos from it. | — | true |
| generate-fromrepo | Generate kudos from main repo contributors | — | false |
| generate-nomerges | Exclude merge commits during generating Kudos from repo. | — | true |
| generate-validemails | Include only valid emails during generating Kudos from repo. | — | true |
| generate-limitdepth | Limit of dependency depth during generating Kudos from repo. | — | 2 |
| ink-validateResult | Validate the ink result from pool compared to the result from Kudos generation. | — | false |
| ink-chunkSize | Chunk size for ink request. | — | 1000 |
| skip-ids | Space separated list of ids/email addresses to skip. | — | "" |
Outputs
no outputs