> For the complete documentation index, see [llms.txt](https://ndocs.wizbot.cc/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ndocs.wizbot.cc/.gitlab/merge_request_templates/merge_request.md). # Merge\_Request #### Description Write here a summary of the change(s) you're proposing and why this merge request would be a necessary or a nice addition to the project. #### Changes Proposed Describe, item by item, all changes you'd like to propose. Write them in a list, one proposition per line. For example: * Adds `DoStuff()` method to service X. * Changes `SomeMethod()` on service Y, so it can handle situation Z better. * Added a try/catch *somewhere*, so an exception is not thrown on the console when *something* happens. * Replaced `AMethod()` by `AnotherMethod()` in *some command* for performance reasons. #### Details Elaborate on the major and minor changes you've made to the source code. Try to explain why you've done something in a certain way. #### Screenshots If applicable, send us screenshots of the result of your changes. #### Notes Write here additional considerations that weren't covered on the previous topics. --- # 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://ndocs.wizbot.cc/.gitlab/merge_request_templates/merge_request.md?ask=&goal= ``` `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.