Skip to content

User configuration


DDQA will always ensure valid config by loading the configuration screen if there are errors or missing required fields.

Input screen

Tip

To locate your personal config file you may run: ddqa config find

GitHub auth

You'll need to create a personal access token (classic) with repo and read:org permissions and, if required by the organization, enable SAML single sign-on.

GitHub token 1 GitHub token 2

The following APIs are used:

  • /search/issues (GET)
  • /repos/{owner}/{repo}/pulls/{pull_number}/reviews (GET)
  • /orgs/{org}/teams/{team_slug}/members (GET)

    Note

    This endpoint is not yet supported when using fine-grained personal access tokens.

Tip

You can configure your GitHub credentials using the DDQA_GITHUB_USER and DDQA_GITHUB_TOKEN environment variables.

Jira auth

You'll need to create an API token with the appropriate scopes.

The following APIs are used:

  • /rest/api/2/issue (POST)
  • /rest/api/2/myself (GET)
  • /rest/api/2/search (POST)
  • /rest/api/2/issue/{issueIdOrKey}/transitions (GET, POST)

Tip

You can configure your Jira credentials using the DDQA_JIRA_EMAIL and DDQA_JIRA_TOKEN environment variables.


Last update: November 16, 2023