Support

Email support@truecount.dev. Include the repository and a link to the pull request or issue, if there is one.

Why didn't Truecount review my pull request?

• It is a draft. Drafts are reviewed when they are marked ready.
• Its author is an outside contributor. Only pull requests from owners, members and collaborators are reviewed without being asked, so strangers cannot use up your allowance. A maintainer can ask for a review (below).
• You pushed new commits. A pull request is reviewed once, when it opens. Ask again for a fresh review.
• Review is turned off in the config file on your default branch.
• Nothing in it was reviewable, for example only lockfiles or generated files changed.
• The config file has an error. Truecount posts a short note on the pull request saying what is wrong, rather than guessing.

Asking for a review

An owner, member or collaborator can comment /truecount review on the pull request, or add the truecount-review label. Either one reviews the pull request's current commit.

Configuring it

Add .github/truecount.yml to your default branch. Truecount reads it from the branch a pull request targets, never from the pull request itself, so a pull request cannot change how it is reviewed.

review:
  enabled: true
  guidelines: .github/review-guidelines.md   # the standard reviews are held to
ignore:
  - "docs/generated/**"                      # never reviewed

Lockfiles, minified files, build output and vendored code are skipped by default. Every file a review leaves out is listed at the bottom of that review.

Removing it

Uninstall the App from your GitHub account or organization settings. To have your records deleted as well, email us; see the privacy policy.

Security

Report a vulnerability to support@truecount.dev with "Security" in the subject. Please do not open a public issue.