# Contributors

## Overview

A contributor is an individual who has developed code changes on a development branch and has opened a PR for review.

## Making Changes

The primary purpose of your new feature branch is to perform code changes.

You can make changes to your file, rename it, or delete it entirely. The Desktop App will render all changes in the *Changes* tab.

![](https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FeyvhmytE1Acg9QUEuJUq%2FDesktopApp_Diff.png?alt=media\&token=cf5de786-df34-4d27-b060-7128b6befd7a)

Once your changes reflect an important enough milestone, you will need to commit them. Navigate to the *Changes* tab and fill in the *Summary* and *Description* fields with information that outlines the changes reflected in that commit.

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2Fy9IwZik2xz4ZTwklru9m%2FDesktopApp_CommitDetails.png?alt=media&#x26;token=8eace525-25c6-4973-966e-75e712529c40" alt=""><figcaption></figcaption></figure>

To store your changes locally, press the Commit button.

![](https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2Fr6yWd8d98nwp9mrpxw5x%2FDesktopApp_CommitPress.png?alt=media\&token=3ea22f6a-a255-466e-a7a7-1af78e84a97a)

{% hint style="info" %}
Committing is covered extensively in the [Making Changes](https://docs.copia.io/docs/git-based-source-control/basic/making-changes) section.
{% endhint %}

## Creating a Pull Request <a href="#create-a-pull-request" id="create-a-pull-request"></a>

Before merging your feature branch with its set of meaningful commits, you will need to create a PR. This step ensures that other colleagues are on the same page about your changes, and in general boosts the quality of your code.

If you haven't already, publish your feature branch by clicking on either of the *Publish Branch* buttons. Publishing makes the Copia server aware of your local branch.

<figure><img src="https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FcD3OhLZsQIXIqZa1a6Q5%2FDesktopApp_Branching_NewBranch_PublishNew.png?alt=media&#x26;token=d5dfe348-cd44-4935-9197-19e1fa05e4b0" alt=""><figcaption></figcaption></figure>

To create your PR, press the *Create Pull Request* button.

![](https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FbsEk2uceTzLPA1A4qrTq%2FDesktopApp_CodeReview_CreateNewPR.png?alt=media\&token=efd13f68-299c-43cd-a850-2f555274055e)

You should be redirected from the Desktop App to the Web App. After confirming that the changes render as expected in the bottom section of the screen, click the *New Pull Request* button.

![](https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FkOPZlPS5IfljDHWel4pN%2FWebApp_CodeReview_ConfirmNewPR.png?alt=media\&token=4269b349-1faf-44f7-9b25-cd1ab2d6f5f7)

{% hint style="info" %}
When you open a new PR, a number will appear next to the branch name in the Desktop App. This number serves as an identifier for that PR.
{% endhint %}

Provide a *Title* and *Description.* Use the editor to provide context for your reviewers and explain the reasons for the proposed changes. You can preview your issue by toggling into the *Preview* tab. When you're finished, click on the *Create Pull Request* button.

![](https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2Fqbp15sZFZ6u9cA7Fzcu4%2FWebApp_CreatingPRDescription.png?alt=media\&token=ea2973d8-a9ca-40eb-9746-51e87d0e349a)

{% hint style="info" %}
You can also drag and drop files and images into your PR.
{% endhint %}

## Adding Reviewers to a Pull Request <a href="#request-a-review" id="request-a-review"></a>

Sometimes, contributors will merge their changes without requesting a review. This is a valid option if the contributor doesn't necessarily require feedback, but they still want to document their change by making a PR.

That said, once a PR has been created, the next step is typically to select who you would like to add as a reviewer.

Click on the *Pull Requests* tab, navigate to your PR, and click on the *Conversation* tab.

![](https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FqUD9HSyczjaZpqGXrJLd%2FWebApp_NavigatePR_AddReviewer.png?alt=media\&token=9b32e012-f759-4949-af16-d0ae0a867da0)

Select the *+Assign Reviewers* dropdown. You will see a list of individuals and Teams that have been assigned to that repository as collaborators. Select the reviewers you want to participate on the PR by either clicking on them or using the *Search for reviewer...* field.

![](https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FJ4IVNeRIdHi6izgJdL7n%2FWebApp_ReviewerSelector.png?alt=media\&token=42f55873-e45e-48f8-a957-de0a0ebcaeb1)

{% hint style="info" %}
Only collaborators on a repository can be assigned as reviewers. To review how to add collaborators to a repository, check out the [Collaborators](https://docs.copia.io/docs/administration/settings#collaborators) section.
{% endhint %}

Reviewers that have been assigned to a PR will appear as chips within the *Conversation* tab.

![](https://3704730939-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F4lSQNVI3DZ15V7kjkMCA%2Fuploads%2FhcNFEbR6PZL3C98vNghE%2FWebApp_NavigatePR_ReviewerAdded.png?alt=media\&token=76b02605-e0a5-4a53-9727-4f068b09fa4d)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.copia.io/docs/git-based-source-control/advanced/code-review/contributors.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
