# Review and Merge

**ALL** contributions to the NRE Labs curriculum must be done via a Pull Request, and Pull Requests can only be merged to `master`with an approving review from a project maintainer. This is **not** a hostile, arbitrary gate-keeping function, but rather a way of ensuring quality remains high for the curriculum.

With the exception of very small Pull Requests to fix things like typos, the chance that your Pull Request will be merged immediately with no suggested changes is very low. However, the good news is, that's okay, and expected. The job of a project maintainer is to get pull requests **merged**, not closed. So, you should expect that your pull request will likely generate questions, and probably some suggested changes. However, you can also expect the following behavior from any project maintainer:

* All comments/questions will be constructive in nature, aimed at helping you as a contributor, and the overall project grow.
* We always want to end every pull request in a "merge" if at all possible. Every question or suggestion is aimed at putting you closer to getting your contribution into the project.

All reviews will be aimed at keeping the quality of the curriculum high. Please read the [Curriculum Quality Standards](/other-resources/curriculum-quality-standards.md) and do your best to ensure that your content strives to meet those standards - it will make the review process a lot smoother.

Once your Pull Request is merged, it will be automatically included in the next [release of the curriculum](/other-resources/curriculum-release-process.md), and published on the site when that process finishes.


---

# 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.nrelabs.io/creating-contributing/review-and-merge.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.