> For the complete documentation index, see [llms.txt](https://developer.gaianet.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.gaianet.ai/getting-started-as-a-developer/contribute-to-the-open-source-project/code.md).

# Code

## **Enhance GaiaNet with Code Contributions** 

Developers can fork our repository on [GitHub](https://github.com/GaiaNet-AI), make improvements or add new features, and submit pull requests (PRs) for review. Regular contributors can be invited to join our core team and take on larger responsibilities.

### Gather Context

Before making your contribution, you want to ensure that it has not already been discussed or done elsewhere. You can skim the repo's README and issues (both open and closed). If you do not see what you're planning to contribute elsewhere, you can:

* **Raise an issue:** this is essentially like starting a conversation or discussion
* **Create a PR:** this will allow you to start work on a solution
* **Visit our** [**Discord channel**](https://discord.com/invite/gaianet-ai)**:** this will allow you to start a conversation or ask for clarification about your contribution. 

###  Starting your Pull Request

1. Fork the repository:
   * Visit the [GaiaNet node](https://github.com/GaiaNet-AI/gaianet-node) repository on GitHub
   * Click the "Fork" button in the top-right corner
   * Select where you want to fork the repository (your personal account or an organization)
2. Clone your forked repository:

   ```
   git clone https://github.com/GaiaNet-AI/gaianet-node.git
   ```
3. Create a new branch for your changes:

   ```
   git checkout -b your-feature-branch
   ```
4. Reference any relevant issues or supporting documentation in your PR
   1. Include screenshots of the before and after, you can drag and drop the images into the body of your PR. 
5. Test your changes to ensure that your changes do not break the project. 
   1. Also be sure that your changes are created with the same style and syntax as your 
6. Commit your changes:

   ```
   git add . 
   git commit -m "Description of your changes"
   ```
7. Push your changes to your fork:

   ```
   git push origin your-feature-branch
   ```
8. Create a pull request:
   * Go to your fork on GitHub
   * Click "Pull request" and select "New pull request"
   * Select your feature branch and submit the pull request

* **Participate in GitHub Activity** By opening issues, suggesting improvements, and engaging in discussions, developers help identify bugs and propose new functionalities. Active participants can earn recognition and rewards.


---

# 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://developer.gaianet.ai/getting-started-as-a-developer/contribute-to-the-open-source-project/code.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.