UPSTREAM TERN / HELP & SETUP
Frequently asked questions
Learn what Upstream Tern records, what repository access requires, and how project build-check settings are used.
For a configured GitHub repository with the required access, Upstream Tern tracks published releases and dependency changes. An “Other repository” source is configuration only and has no provider checks.
No. Saving a repository source or URL stores project configuration; it does not connect a GitHub account, grant repository read access, or authorize pull-request writes. Private monitoring also requires a verified token and monitoring access.
No. Saving records the commands as configuration; it does not run them. Configured commands are used to evaluate monitored changes.
A failed configured check produces a failure report and candidate fix for maintainer review. The candidate is a suggested next step; it does not automatically open a pull request.
The project setup guide documents the accepted values, limits, and behavior for each field.
Read the project setup guideNeed accepted values, field limits, or examples?
Read the project setup guide