A light-weight lint workflow when using GitHub along with JIRA for project management. Ported from pivotal-lint for similar usage with Atlassian's Jira Software.

• Jira-lint 🧹
  • Installation
    • Semantic Versions
  • Features
    • PR Status Checks
    • PR Description & Labels
      • Description
      • Labels
      • Soft-validations via comments
    • Options
    • Skipping branches
  • Contributing
  • FAQ

To make jira-lint a part of your workflow, just add a jira-lint.yml file in your .github/workflows/ directory in your GitHub repository.

name: jira-lint
on: [pull_request]

jobs:
  jira-lint:
    runs-on: ubuntu-latest
    steps:
      - uses: cleartax/jira-lint@master
        name: jira-lint
        with:
          github-token: ${{ secrets.GITHUB_TOKEN }}
          jira-token: ${{ secrets.JIRA_TOKEN }}
          jira-token: https://your-domain.atlassian.net
          skip-branches: '^(production-release|master|release\/v\d+)$'
          skip-comments: true
          pr-threshold: 1000

It can also be used as part of an existing workflow by adding it as a step. More information about the options here.

If you want more stability in versions of jira-lint than @master you can also use the semantic releases for jira-lint.

Example:

# ...
steps:
  - uses: cleartax/[email protected]
    name: jira-lint
    # ...

jira-lint adds a status check which helps you avoid merging PRs which are missing a valid Jira Issue Key in the branch name. It will use the Jira API to validate a given key.

When a PR passes the above check, jira-lint will also add the issue details to the top of the PR description. It will pick details such as the Issue summary, type, estimation points and labels and add them to the PR description.

jira-lint will automatically label PRs with:

• A label based on the Jira Project name (the project the issue belongs to). For example, if your project name is Escher then it will add escher as a label.
• HOTFIX-PROD - if the PR is raised against production-release.
• HOTFIX-PRE-PROD - if the PR is raised against release/v*.
• Jira issue type (based on your project).

jira-lint will add comments to a PR to encourage better PR practices:

A good PR title

A comment discouraging PRs which are too large (based on number of lines of code changed).

Since tokens are private, we suggest adding them as GitHub secrets.

The Jira token is used to fetch issue information via the Jira REST API. To get the token:-

1. Generate an API token via JIRA
2. Create the encoded token in the format of base64Encode(<username>:<api_token>). For example, if the username is [email protected] and the token is 954c38744be9407ab6fb, then [email protected]:954c38744be9407ab6fb needs to be base64 encoded to form Y2lAZXhhbXBsZS5jb206OTU0YzM4NzQ0YmU5NDA3YWI2ZmI=
3. The above value (in this example Y2lAZXhhbXBsZS5jb206OTU0YzM4NzQ0YmU5NDA3YWI2ZmI=) needs to be added as the JIRA_TOKEN secret in your GitHub project.

Note: The user should have the required permissions (mentioned under GET Issue).

Since GitHub actions take string inputs, skip-branches must be a regex which will work for all sets of branches you want to ignore. This is useful for merging protected/default branches into other branches. Check out some examples in the tests.

jira-lint already skips PRs which are filed by bots (for eg. dependabot). You can add more bots to this list, or add the branch-format followed by the bot PRs to the skip-branches option.

Follow the instructions here to know more about GitHub actions.