> For the complete documentation index, see [llms.txt](https://dev.cubrid.org/dev-process/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.cubrid.org/dev-process/dp-en/gh-guide/git-feature-branch.md).

# Feature Branch

In the case of developing new features and fix bugs, you can ask the CUBRID committers to create a *feature* branch in the *develop* branch.

Create the name of the Feature Branch as follows: 

* feature/\<name>

example) feature/javasp, feature/tde, feature/truncate\_table

* If you set the name as above, The Github Checks can be performed automatically.

The main purpose of the *feature* branch is to divide the code review into several rounds when the size of the code to be merged is large. Rather than merging only a part of the function in the *develop* branch, the *feature* branch will conduct efficient code review with multiple PRs and merge them more reliably in the *develop* branch.

Note that git commands are managed as follows:

```
# 1. create feature branch 
git remote add upstream 
http://github.com/cubrid/cubrid

git fetch upstream
git checkout -b feature/my_feature upstream/develop
git push -u upstream feature/my_feature

# 2. Multiple PRs on github
git fetch upstream
git checkout -b CBRD-OOOOO upstream/feature/my_feature
   # many commits (development in progress)
git push -u origin CBRD-OOOOO
   # Code review after PR creation
# 2. Repeat multiple times == multiple review rounds

# 3. sync with develop by merge (do not PR commit for sync)
git checkout feature/my_feature
git fetch upstream
git merge upstream/feature/my_feature // should be fast-forward merging
git merge upstream/develop
git push upstream feature/my_feature

# 2. Repeat multiple times == multiple review rounds

git push origin CBRD-OOOOO

# Create PR for CBRD-00000
```

\*Note: *Feature* branches can be created at any time, and will be deleted after the feature has been reviewed and merged into the *develop* branch.


---

# 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://dev.cubrid.org/dev-process/dp-en/gh-guide/git-feature-branch.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.