> For the complete documentation index, see [llms.txt](https://wiki.nushackers.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.nushackers.org/orbital/git/collaborative-workflows/branch-and-pr-workflow.md).

# Branch and PR Workflow

While the [Fork and PR Workflow](/orbital/git/collaborative-workflows/fork-and-pr-workflow.md) is the recommended workflow, you could also work collaboratively by creating PRs through the original repository (i.e. no forks involved).

This may be simpler to setup for smaller projects (like Orbital), but we still highly recommend following the [Fork and PR Workflow](/orbital/git/collaborative-workflows/fork-and-pr-workflow.md) instead.

This workflow is very straightforward:

1. Clone the original repository
2. Create a local branch
3. Make changes to the local branch
4. Push the local branch to the original repository
5. Make a PR from the local branch to the `main` branch

While it is very simple, it is also very error prone as pushing directly to the original repository may result in directly overriding changes in the original repository if you are not careful and you may not even have the permissions to push directly to the original repository (this is the case for most open-source projects).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://wiki.nushackers.org/orbital/git/collaborative-workflows/branch-and-pr-workflow.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.