TeireDocs
ChangesScanDashboardTry Teire
GuideEcosystems & APIsNemotron on Token FactoryBuild
ChangesScanDashboard
Try Teire
What Teire doesQuickstartHow Teire worksAnatomy of a Teire PRThe life of a Teire PR

Use it

Public scan and dry runDashboardAsk Teire@teire commandsConfiguration (teire.yml)dependabot.ymlPrivate registries

Help

TroubleshootingCompared with Dependabot and Renovate
Guide

@teire commands

Comment on any issue or pull request to rescan, fix, ignore, rebase, explain or pause. Teire answers in the thread and links the live run.

One comment, one answer. A comment such as '@teire fix zod' on GitHub; Teire reacts with eyes at once, checks your write access on GitHub, starts the run (live on its page) and replies in the thread with the run's link.
  1. @teire fix zoda comment
  2. seconds
  3. πŸ‘€read at once
  4. or refused
  5. Write accesschecked on GitHub
  6. starts
  7. The runlive on its page
  8. in the thread
  9. A replywith the run's link
Every command: read at once, checked against your access, answered in the thread.

Start a line of a comment with the command, on any issue or pull request in the repository. Teire reacts with πŸ‘€ as soon as it reads the comment, then replies. Commands need write, maintain or admin access to the repository. Anyone else gets "Teire commands need write access to this repository, so nothing was run."

@teire help replies with this table:

CommandWhat it does
@teire rescanScan the default branch again
@teire fix <change or package>Start a fix run now (also: tick "Fix now" in the Dashboard issue)
@teire ignore <change, package or provider:name>Stop reporting it; closes its open PR
@teire unignore <change, package or provider:name>Report it again
@teire ignore <package> major|minor|patchSkip that kind of update for the package; on a Teire PR, @teire ignore major names its package and closes it
@teire show ignoresWhat this repo ignores, from teire.yml and from commands
@teire rebaseOn a Teire PR: re-apply on the current base and verify again
@teire recreateOn a Teire PR (even closed): run the fix again from scratch
@teire reverifyOn a Teire PR: run your checks again on it as it stands, before and after, and set its evidence
@teire open-draftOn a Teire "needs a human" issue: open its best diff as a draft PR marked unconfirmed
@teire explainOn a Teire PR or issue: the evidence behind it
@teire configThe resolved config, with where each value came from
@teire pause / @teire resumeStop or restart scans and PRs for this repo
@teire fix-mode automatic|ask|offHow Teire fixes here: on its own (the default), only when a person asks, or not at all
@teire pause-fixes / @teire resume-fixesShorthand for fix-mode off and back to the installation's default
@teire wrong <reason>Tell us a finding is a false positive or negative
@teire helpThis list

What each one does

Without a comment

The same actions exist in two other places:

  • The Dashboard issue. Tick Rescan now, Fix now, Upgrade and check, Rebase or Unignore.
  • The web dashboard. Rescan, Pause, Resume, Fix now, Ignore and Unignore on the repository page, Fix now from the estate on the Overview, Fix in all on Changes for you, and every one of them through Ask Teire with Confirm.

Both apply the same write-access rule. See Dashboard.

Teire posts no progress comments while it works. The live view is the run page, linked from the reply, from the PR's footer and from the Teire check run's details.

Ask Teire

Ask about your repositories, findings, runs and changes in plain words. Ask Teire reads what Teire knows, answers with cards from the real records, and changes something only when you click Confirm.

Configuration (teire.yml)

One optional file decides what Teire upgrades, how many PRs it opens, which checks it runs and what it reads. Every key has a default, and a mistake never stops a scan.

On this page

What each one doesWithout a comment