> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/contributing-content/contribution-sla.md). # Contribution SLA You can contribute content to the Cortex XSIAM Marketplace by contributing through a GitHub pull request on the public [content repository](https://github.com/demisto/content). For more information, see [Contributing content](/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/contributing-content.md). A review phase begins with the opening of the GitHub pull request containing your changes or new content. #### Cortex XSIAM content team commitments Once your PR is open, the content team commits to the following time frames: 1. After the PR is opened, a reviewer is assigned to your PR and publishes the initial response to your submission within five business days. 2. If you are asked to make changes, you need to make those changes, and add a corresponding message in the pull request. Your reviewer responds within three business days. You might have multiple rounds of fixes. These commitments are the same for each round. 3. Your reviewer is available for any questions during the review process. You can contact your reviewer via the PR itself or on Slack ([DFIR Slack Community](https://start.paloaltonetworks.com/join-our-slack-community)). 4. Once your PR is approved and merged by your reviewer, an internal PR including your changes is opened within an hour. The internal PR allows us to run our internal validity and security checks on your final code. The internal PR is merged within three business days. If during the internal PR phase we discover issues related to the code changes made in the contribution, the contributor may be asked to help resolve them. 5. Once the internal PR is merged, your changes are published in the Marketplace within three business days. #### Contributor commitments The content team requires contributors to: * Provide the content team with as much information as possible about changes made or about new content you have created. Provide this information in the pull request body by filling in the template. * Register your contribution by filling out the contribution registration form, and sign the [CLA](https://github.com/demisto/content/blob/master/docs/cla.pdf) (Contributor License Agreement). The review process does not start until those forms are completed. Links to the Contribution registration form and to the CLA appear on your PR: ![](/files/TBpkEBCqyTw143CnAHEI) ![](/files/peGoJs4IbJePovkvtdbQ) * Provide the content team with a [recorded demo session](/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/contributing-content/contribution-demo-preparation.md) that demonstrates your changes. Add the link to the contribution registration form. * Check the status of the build of your PR once it is completed. If the build includes errors, try to solve them. For more information, see [the build process](/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/contributing-content/pull-request-conventions.md). * During the review process, monitor your PR. Your reviewer may add comments to the PR, asking questions and requesting changes. To expedite the review process for your contribution, respond to the reviewer's code review and apply the required changes within 14 days. Stale pull requests can be closed.

Note

Once your pull request is reviewed, only add or update content items that were requested during the review process. If you have new content items to add, open a new pull request. If you are not sure whether to open a new pull request, consult the reviewer.

* If your contribution includes changes in an Cortex XSIAM supported content pack, you must conform to the Cortex XSIAM code and documentation standards, and add unit tests and a test-playbook to test your code. For more information see [Python code conventions](/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/integrations-and-scripts/developing/python-code-conventions.md), [Documentation](/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/documentation.md), [Unit testing](/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/testing/unit-testing.md), and [Test playbooks](/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/testing/test-playbooks.md). While the content team tries to merge and publish your changes as quickly as possible, the duration of the review process depends on many factors including the level of support of the edited content pack, the number and complexity of changes, and various validations and security tests. --- # 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://cortex-docs.paloaltonetworks.com/cortex-xsiam-developer-guide/cortex-xsiam-development-guide/contributing-content/contribution-sla.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.