exogee-technology/action-jira-linker
Add JIRA issue details to your GitHub pull request.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
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-user | JIRA username (email address) of the user that created the token. Can be passed in using {{ secrets.JIRA_USER }} | 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" | yes | — |
| comment-header | A message that will be added to the top of the PR comment in markdown format. Default is "". | no | "" |
| comment-trailer | A message that will be added to the bottom of the PR comment in markdown format. Default is "". | no | "" |
| fail-on-error | Set this to true if you want action-jira-linker to fail the PR if it cannot find a JIRA issue. Default is false. | no | false |
| force-update | Set this to true if you want action-jira-linker to add the comment for PRs that have not been recently opened at the risk of creating duplicate comments, this can be useful while testing the action integration. | no | false |
| update-body | Update the issue body with the comment instead of adding a comment | no | false |
| include-title | Add jira ticket summary to generated link | no | false |
| link-prefix | Text which is added before the jira ticket link | no | JIRA Issue: |
Outputs
no outputs