> For the complete documentation index, see [llms.txt](https://releaseowl.gitbook.io/releaseowl-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://releaseowl.gitbook.io/releaseowl-docs/releaseowl-user-guide/sap-btp/git-ops.md).

# GIT Ops

## **Prerequisites**

1. Create new project of type SAP BTP (MTAR) or SAP HANA XSA (MTAR)
2. Register BTP Credentials and BTP Environment with ReleaseOwl.
3. Create and run one or more Build Pipelines with changes done at GT repository level.

### **Commits**

1. When you trigger the build, all the commits done on the repository right from the previous build run are pulled and shown to the user.
2. The commits done can be selected and assigned to a user story to track their deployment.<br>

<figure><img src="/files/ZlPISoW78hT25PTdrKxO" alt=""><figcaption></figcaption></figure>

### **Assign User Stories to GIT Commits**

1. Select the user story and click Assign User Story. Select the user story.\ <br>

<figure><img src="/files/A36nvbuYN0irhY9HMzp6" alt=""><figcaption></figcaption></figure>

2. You can also automatically assign a user story to a particular commit by specifying #ID in the Commit message that you specify in BitBucket or GITHub.

{% hint style="info" %}
**Note :** Mention the external user story ID if project is integrated with external ALM tool, else provide ReleaseOwl user story ID.
{% endhint %}

<figure><img src="/files/csSMw0eqx7wKTU2hfbPZ" alt=""><figcaption></figcaption></figure>

3. Thereafter when you trigger the build and click on commits, you get to see that the commit gets assigned to the user story automatically and the commit message given in the **Bitbucket** or **GITHub i**s seen under the **Commit Message** as shown below:

<figure><img src="/files/6AwdyODx3d00kp9LdBFM" alt=""><figcaption></figcaption></figure>

<figure><img src="https://www.docs.releaseowl.com/assets/img/Git-Ops-4.jpg" alt=""><figcaption></figcaption></figure>


---

# 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://releaseowl.gitbook.io/releaseowl-docs/releaseowl-user-guide/sap-btp/git-ops.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.
