# How to contribute code

GitHub is our primary platform for collaborative software development within the Simpler Grants community. This guide will help you get started and make the most out of your code contribution experience.

{% hint style="info" %}
**Looking for work?**

Our development team curates "help wanted" issues for open source developers like you to help out with on [GitHub](https://github.com/HHS/simpler-grants-gov/labels/help%20wanted).
{% endhint %}

## Contribution Guidelines

### A. Code style and standards

* Follow the established code style and standards.
* Use clear and descriptive variable names, comments, and documentation where necessary.

### B. Testing

* Write tests for your code changes to ensure they function as expected
* Run exiting tests and ensure they pass before submitting your pull request

### C. Documentation

* Update any relevant documentation in the README files to reflect changes

## Getting Started

### 1. Create a Fork

Create a new fork of the simpler grants.gov repository for your changes. Fork names should conform to the simpler grants naming convention

```
<github username>/<GitHub Issue #>-simple-ticket-description
```

For example

```
btabaska/1234-updating-api-with-new-header
```

Next, create a feature branch using the following command, replacing feature-branch-name with a name that follows our branch naming schema

```
git checkout -b feature-branch-name
```

### 2. Clone the repository

Clone the forked repository to your local machine using the following command:

```
git clone https://github.com/<your-github-username>/<repository-name>.git
```

Instruction on setting up the local development environment can be found in the README of the repository.

API Development Instructions [API Development Instructions](https://github.com/HHS/simpler-grants-gov/blob/main/documentation/api/development.md)

Front End Development Instructions [Front End Development Instructions](https://github.com/HHS/simpler-grants-gov/blob/main/frontend/README.md)

{% hint style="info" %}
**Need help with your local development environment?**\
\
Post in the [Discourse forum](https://forum.simpler.grants.gov/) if you're having issues. We can walk you through the process of resolving blockers.
{% endhint %}

### 3. Make & Commit changes

Make your desired changes to the codebase using your preferred editor. Once you're done, stage and commit your changes:

```
git add . 
git commit -m "Brief Description of changes"
```

### 4. Push Changes

* Push your changes to your forked repository on GitHub using the following command:

```
git push origin feature-branch-name
```

### 5. Run code quality checks to verify changes

Frontend:

On the frontend of the project we enforce formatting, linting, typescript checks and unit testing before a code change can be accepted.

To run frontend tests:

{% code overflow="wrap" %}

```
// run linting to check that lint rules are being met
npm run lint
// run formatting to ensure that document formatting is correct. This will attempt to auto-fix simple issues with formatting
npm run format
// run type checks to ensure that typescript rule requirements are being met
npm run ts:check
// run unit tests to validate that defined component tests are not failing
npm run test 
```

{% endcode %}

API

In the API of the project we enforce formatting, linting and unit tests. These all must pass before code changes can be accepted.

To run API tests:

{% code overflow="wrap" %}

```
// run linting to check that lint rules are being met
make lint
// run formatting to ensure that document formatting is correct. This will attempt to auto-fix simple issues with formatting
make format
// run unit tests to validate that defined unit tests are not failing
make test
```

{% endcode %}

### 6. Create a Pull Request

a. Navigate to your forked repository on GitHub

b. Click on the Pull Request button

c. Fill out the pull request form

d. Validate that GitHub automated integration testing is not failing. If it is go back and make changes to your code until all tests are passing again.

e. Submit the pull request for review by other developers within the community

\
Example pull request form:

```
## Summary
Fixes #(ISSUE)

### Time to review: ___x mins___
## Changes proposed
> // Update with a short description of what you changed

## Context for reviewers
> // Provide context for the PR reviewer
```

### 7. Review process

#### a. Assign reviewers

* Assign reviewers to your pull request who are knowledgeable about the project and can provide valuable feedback

#### b. Feedback and iteration

* Address any feedback or comments from reviewers promptly
* Make necessary changes and iterate on your code until it meets the projects standard to be accepted
* Once your pull request has been approved it will be merged into the main branch and deployed as necessary.

## Change log

Major updates to the content of this page will be added here.

<table><thead><tr><th>Date</th><th width="246">Update</th><th>Notes</th></tr></thead><tbody><tr><td>2/12/2024</td><td>Initial Content</td><td>Updated with Initial content</td></tr><tr><td>10/3/2024</td><td>Updated content</td><td>Updated content for hackathon</td></tr><tr><td></td><td></td><td></td></tr></tbody></table>


---

# 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://wiki.simpler.grants.gov/get-involved/github-code.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.