abhinav-sharma-corpit/jira-lint
Add JIRA issue details to your GitHub pull request.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stalelast commit Jun 5, 2023
- License
- MIT
- Runtime
- Deprecated runtime
Pinned Snippet
uses: abhinav-sharma-corpit/jira-lint@dfaeb983ca74fb394c2ce92cb89d7e5f79a3f306 # no releases — HEAD as of 2026-07-12tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| github-token | Token used to update PR description and add labels. Can be passed in using {{ secrets.GITHUB_TOKEN }} | yes | — |
| jira-token | API Token used to access the JIRA REST API. Must have read access to your JIRA Projects & Issues. | yes | — |
| jira-base-url | The subdomain of JIRA cloud that you use to access it. Ex: "https://your-domain.atlassian.net" | no | https://fexle.atlassian.net |
| skip-branches | A regex to ignore running on certain branches, like production etc. | no | "" |
| skip-comments | A boolean if set to true, will skip adding lint comments for PR title. | no | false |
| pr-threshold | An `Integer` based on which jira-lint add a comment discouraging huge PRs. Is disabled by `skip-comments` | no | 800 |
| validate_issue_status | Set this to true if you want jira-lint to validate the status of the detected jira issues | no | false |
| allowed_issue_statuses | A comma separated list of acceptable Jira issue statuses. You must provide a value for this if validate_issue_status is set to true Requires validate_issue_status to be set to true. | no | In Progress |
Outputs
no outputs