contractify/Add Jira info to pull request
Automatically add Jira info to a pull request
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Activelast commit Jul 6, 2026
- License
- MIT
Pinned Snippet
uses: contractify/add-jira-info@8cebaa1ebd0d7be32ff45e58fffd049eb0035675 # v1.21.0tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| github-token | The GITHUB_TOKEN secret | — | — |
| jira-username | Username used to access the Jira REST API. Must have read access to your Jira Projects & Issues. | — | — |
| 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" | yes | — |
| jira-project-key | Key of project in jira. First part of issue key, will grab project keys using provided jira credentials if not provided. | no | "" |
| add-label-with-issue-type | If set to true, a label with the issue type from Jira will be added to the pull request | no | true |
| issue-type-label-color | The hex color of the label to use for the issue type | no | FBCA04 |
| issue-type-label-description | The description of the label to use for the issue type | no | Jira Issue Type |
| add-jira-key-to-title | If set to true, the title of the pull request will be prefixed with the Jira issue key | no | true |
| add-issue-type-emoji-to-title | If set to true, an emoji representing the Jira issue type will be prepended to the pull request title | no | true |
| add-jira-key-to-body | If set to true, the body of the pull request will be suffix with a link to the Jira issue | no | true |
| add-jira-fix-versions-to-body | If set to `true`, the body of the pull request will be suffix with the `fixVersions` from to the Jira issue | no | true |
Outputs
no outputs