jhesch/Dirty Bits Action
Identifies the parts of a repository that need to be built, tested, deployed, etc. depending on which files have changed
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
Inputs
| name | description | required | default |
|---|---|---|---|
| rules-file | Path to YAML file containing rules | yes | — |
| results-file | Path to file on runner to write JSON results | no | — |
| token | GitHub authentication token | no | ${{ github.token }} |
| repository | GitHub repository | no | ${{ github.repository }} |
| base | Base commit SHA or tag name, automatically detected by default | no | — |
| head | Head commit SHA or tag name, automatically detected by default | no | — |
Outputs
| name | description |
|---|---|
| all-clean | A boolean value to indicate whether all repo bits are marked clean |
| all-dirty | A boolean value to indicate whether all repo bits are marked dirty |
| some-dirty | A boolean value to indicate whether at least one repo bit is marked dirty |
| clean-bits | A space-separated list of the repo bits that are marked as clean |
| dirty-bits | A space-separated list of the repo bits that are marked as dirty |
| json-results | The results as a JSON string |