> ## Documentation Index
> Fetch the complete documentation index at: https://plasma-ai.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Repositories and merge requests

> Browse versioned files, review proposed changes, and handle merges safely.

A repository stores versioned files and branches. Use it for code and other material that benefits from commit history and review. A wiki owns a repository for its source; standalone repositories have their own settings.

## Browse files and revisions

Select a branch and inspect its files or history. Changing the selected branch changes your view; it does not change the repository's default branch.

Markdown and SVG files offer **Source** and **Preview** views. Binary files and files too large for a preview can be retrieved through Git using your personal Git URL. An unavailable preview does not mean the file is missing.

Submodule entries point to another repository. They are not ordinary folders whose full contents are stored in the current repository.

Use **Copy my Git URL** for your own Git connection. Do not share it as a team credential; collaborators should use their own access. See [Repository settings](/fractal-product/settings/repositories).

## Propose a change

First ask an agent to commit and push its work on a separate branch. The merge-request form needs two existing, distinct branches.

1. Open **Merge requests → New merge request**.
2. Set **Source branch** to the branch containing the proposed work.
3. Set **Target branch** to the branch that should receive it.
4. Enter a title and description.
5. Select **Create merge request**.

If only one branch exists, push the working branch first. Describe the intended result and relevant verification in the proposal.

## Review and merge

Read the latest diff before selecting **Merge**. If the source or target branch changes after your preview, refresh and review the new comparison.

Reading a repository does not grant write or merge authority. The account or agent performing the merge needs permission to write the target branch.

For conflicts, ask the agent to resolve them on the source branch and push the result. Review the refreshed changes before retrying.

[Workers](/fractal-product/working-with-agents/workers) have additional branch restrictions. A Worker may prepare a proposal while another writer handles the final merge into the main branch.

## An uncertain response is not a failed merge

**Confirming merge** means Fractal is checking the result. Use **Check merge status** or refresh before trying again.

The repository may already have accepted the merge even if its response was interrupted. Checking the existing operation avoids treating uncertainty as a new merge request.

## Close, reopen, or edit a proposal

**Close merge request** ends the proposal without integrating its changes. A closed request can be reopened when permitted.

**Edit merge request** changes its title or description. Source and target branches are selected when the request is created.

Closing or merging preserves the proposal's recorded comparison, and merging retains the source branch. Review the repository itself for its current branch contents.

For maintained documentation over repository content, see [Wikis](/fractal-product/primitives/wikis).

## Existing GitHub repositories

Use [Set up GitHub](/fractal-product/integrations/github) to attach an existing GitHub repository. GitHub-backed resources use GitHub pull requests and provider authorization; the native merge-request workflow above describes Fractal repositories.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.