UPSTREAM TERN / PROJECT SETUP

Configure a project

This guide follows the fields in project creation and editing. Project name and repository visibility are set at creation; repository URL, dependency specifications, and build-check commands can also be updated when editing a project.

  1. FIELD 01

    Project name

    Creation only

    A trimmed text name for this project in your workspace. Enter 2 to 80 characters after leading and trailing whitespace is removed.

    Example

    Linux gateway build

  2. FIELD 02

    Repository URL

    Create and edit

    Enter a valid HTTP or HTTPS repository URL without an embedded username or password. It identifies the repository source. The form describes release and dependency-graph checks for GitHub repositories.

    Example

    https://github.com/team/project

    Private repository access is unavailable until the owner supplies an authorized provider connection. This saves the repository address only. Private monitoring also requires verified repository access and monitoring access.

  3. FIELD 03

    Repository visibility

    Creation only

    Choose Public or Private to record the repository visibility when creating the project. This field is not available in the current edit form. Choosing Private does not grant repository access.

  4. FIELD 04

    Dependency specifications

    Create and edit

    This optional field accepts one free-form specification per line. Each non-empty line is trimmed, must contain text, and can be at most 300 characters; you can enter up to 50 non-empty lines.

    Examples

    • libssl-dev
    • cmake >= 3.24

    GitHub dependency changes come from repository manifests; matching names are annotated when possible. Other lines are kept as setup notes and are not resolved against a guessed registry.

  5. FIELD 05

    Build-check commands

    Create and edit

    This optional field accepts one command per line. Each non-empty line is trimmed, must contain text, and can be at most 300 characters; you can enter up to 50 non-empty lines.

    Examples

    • make test
    • cargo test

    These commands describe how the project is built. They are saved as configuration and are not executed when you save.