factory-environment-setup

Topics in the source

• Set up a factory repository environment
• Prepare a reviewable plan
• Apply the reviewed plan

Work for one configured factory repository binding at a time. The repository's code host and issue tracker are separate identities: GitHub and GitLab may serve both roles; Jira Cloud supplies issues for a GitHub or Bitbucket Cloud/DC code host. Follow the actual binding. Do not infer a tracker from a repository URL, or treat an inaccessible history as evidence that no tools are needed. Use the configured provider's read interface: GitHub issues and pull requests; GitLab issues and merge requests; Jira Cloud issues plus the linked code-host pull requests; or Bitbucket Cloud/DC pull requests plus the bound Jira issues. Preserve host and project identity when linking records. Ask for missing read access rather than substituting another provider's history. 1. Identify the binding, factory agent, code host, tracker, base branch, current runner image digest, and operator-owned Helm values. Read-only access is sufficient for planning. Keep private repository and deployment identifiers out of public upstream records. 2. Read the repository's verification declaration, CI workflows, manifests, lockfiles, and runner inputs at one pinned base commit. Inspect a bounded, stated sample of recent

This is an excerpt. Refer to the complete source and its current requirements.