g2crowd/Required JIRA Approvals
Check labels for convention ending with -required/-approved
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Mar 15, 2024
- License
- None
- Runtime
- Deprecated runtime
Pinned Snippet
uses: g2crowd/required-approvals-action@f15d506d8843c8eea4492edf485a8c38312c1693 # v1.6tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| commit_message | The commit message that may contain the JIRA story. | yes | — |
| pr_title | The pull request title that may contain the JIRA story. | yes | — |
| jira_user | The email of the jira user. | yes | — |
| jira_token | The API token associated to the user. | yes | — |
| jira_url | The base URL for jira | yes | — |
| default_labels | Assumed required labels | no | design-qa-required|product-qa-required |
| required_suffix | Append this to the end of a label to mark it required | no | required |
| approved_suffix | Append this to the end of a label to mark it approved | no | approved |
Outputs
no outputs