dimvic/JIRA integration

JIRA integration

Trust Signals

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-username	Username (or email) used to access the JIRA REST API. Must have read access to your JIRA Projects & Issues.	yes	—
jira-token	API Token used to access the JIRA REST API. Must belong to <jira-username>.	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-regexp	Regexp referenced JIRA issue's code project key should match.	no	""
pr-enforce-issue-exists	Whether to enforce JIRA issue codes existence in PR title.	no	true
pr-enforce-issue-type-regexp	Regexp JIRA issue's type to match a regular expression (ie '^epic$').	no	""
pr-update-title	Whether to update PR title with JIRA issue summary.	no	true
pr-update-description	Whether to update PR body to include JIRA issue description.	no	true
pr-issue-code-regexp	Regexp used to match JIRA issue code in PR title.	no	^\[(\w+[_-]\d+)\]
pr-skip-base-ref-regexp	Skip checks for PRs with a base ref matching this regexp (target ref: ie "^deploy/").	no	""
pr-skip-head-ref-regexp	Skip checks for PRs with a head ref matching this regexp (source ref: ie "^main$", "^hotfix/", "^(main\|hotfix/.*)$").	no	""
pr-skip-user-regexp	Skip checks when PR user matches this regexp (ie "^dimvic$").	no	""

no outputs