> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ospribrain.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Git and Publishing

> Create or adopt repositories, review changes, authenticate Git, and understand the protected publish flow.

OSPRI Science includes portable Git in Full Workstation.

## Create or adopt

* **Create** makes a new coding-project folder from an available template and can initialize Git.
* **Adopt** attaches OSPRI to an existing safe folder after ownership checks.
* **Clone** can be run as an approved Git command when authentication is already available.

## Git identity and authentication

OSPRI does not currently provide a Git-provider credential form in Connections. Configure the repository identity and an authentication method such as SSH or supported system credentials before pushing.

Do not paste a long-lived access token into a chat.

## Safe commit flow

<Steps>
  <Step title="Inspect status and instructions">
    Read repository instructions and identify unrelated modified or untracked files.
  </Step>

  <Step title="Make the focused change">
    Edit only files required by the task.
  </Step>

  <Step title="Run the real project checks">
    Use the repository's own test, lint, typecheck, build, and validation commands.
  </Step>

  <Step title="Review the exact diff">
    Confirm secrets, generated local files, and unrelated work are not staged.
  </Step>

  <Step title="Commit and push">
    Use the repository's configured identity. Push only after authentication and required approvals succeed.
  </Step>
</Steps>

## Conflicts and failed commands

A failed pull, merge, checkout, rebase, or push is not guaranteed to leave the working tree unchanged. Inspect `git status`, the current branch, and the diff before retrying. Resolve conflicts deliberately and rerun the project checks.

Force pushes and destructive resets need explicit scrutiny because they can replace remote or local history.

## Public publishing

The current public publish control applies to a protected production-build preview, not arbitrary local files or an entire repository. Its flow validates a safe slug and controlled destination, then requires explicit consent and exact-name confirmation before a public alias is created.

<Warning>
  “Push this branch” and “publish this preview publicly” are different actions. State which one you mean.
</Warning>