<commit_before># How to Release a Git Repository
> The process of setting up and releasing a Git repository when you develop a WSO2 product is explained below. For the full list of features and capabilities available in this Kernel version, see the [root README.md file](../../README.md). 

The following are the steps for creating and releasing a Git repository:

* **[Setting up a Git Repository](#setting-up-a-git-repository)**
* **[Releasing a Git Repository](#releasing-a-git-repository)**

## Setting up a Git Repository

With the git based model, releases can be made easy using the `maven-release-plugin` and nexus staging repository. The following are the common guidelines for releasing from any git repository under a WSO2 user:

> Note that WSO2 approval is required for setting up git repositories under a WSO2 user. Also, this is a one-time process, which does not have to be repeated.

### Step 1: Creating the repository

The following guidelines refer to carbon4-kernel as the sample project being released from git:

1. Create a “Repository Target” in [http://maven.wso2.org/nexus/](https://maven.wso2.org/nexus/#welcome) that matches the `groupID` of the project and add a “Pattern Expression”. This pattern expression is used by nexus to automatically determine the staging profile. Shown below are the values used when creating a "Repository Target" for the `carbon-kernel` project in git.

 * **Name:** `org.wso2.carbon`

 * **Repository Type:** `Maven2`

 * **Pattern Expression:** `.*/org/wso2/carbon/.*`

2. Create a nexus “Staging Profile” for the project in [http://maven.wso2.org/nexus/](https://maven.wso2.org/nexus/#welcome), if it is not already created. The name of the profile should match the project's `groupID`. For example, the name of the profile for the `carbon4-kernel` project should be `org.wso2.carbon`.

   a. Select the "Repository Target" that was created in step 1 above as the "Repository Target" for this profile.

   b. Select the `Releases` repository in [http://maven.wso2.org/nexus/content/repositories/releases/](http://maven.wso2.org/nexus/content/repositories/releases/) as the “Release Repository” for all staging profiles.<commit_msg>Update SettingUpaGitRepository.md<commit_after># How to Release a Git Repository
> The process of setting up and releasing a Git repository when you develop a WSO2 product is explained below. For the full list of features and capabilities available in this Kernel version, see the [root README.md file](../../README.md). 

The following are the steps for creating and releasing a Git repository:

* **[Setting up a Git Repository](#setting-up-a-git-repository)**
* **[Releasing a Git Repository](#releasing-a-git-repository)**

## Setting up a Git Repository

With the git-based model, releases can be made easy using the `maven-release-plugin` and the nexus staging repository. The following are the common guidelines for releasing from any git repository under a WSO2 user:

> Note that WSO2 approval is required for setting up git repositories under a WSO2 user. Also, this is a one-time process, which does not have to be repeated.

### Step 1: Creating the repository

The following guidelines refer to carbon4-kernel as the sample project being released from git:

1. Create a “Repository Target” in [http://maven.wso2.org/nexus/](https://maven.wso2.org/nexus/#welcome) that matches the `groupID` of the project and add a “Pattern Expression”. This pattern expression is used by nexus to automatically determine the staging profile. Shown below are the values used when creating a "Repository Target" for the `carbon-kernel` project in git.

 * **Name:** `org.wso2.carbon`

 * **Repository Type:** `Maven2`

 * **Pattern Expression:** `.*/org/wso2/carbon/.*`

2. Create a nexus “Staging Profile” for the project in [http://maven.wso2.org/nexus/](https://maven.wso2.org/nexus/#welcome), if it is not already created. The name of the profile should match the project's `groupID`. For example, the name of the profile for the `carbon4-kernel` project should be `org.wso2.carbon`.

   a. Select the "Repository Target" that was created in step 1 above as the "Repository Target" for this profile.

   b. Select the `Releases` repository in [http://maven.wso2.org/nexus/content/repositories/releases/](http://maven.wso2.org/nexus/content/repositories/releases/) as the “Release Repository” for all staging profiles.
{'fraction_non_alphanumeric': 0.09573502722323049, 'fraction_numerical': 0.009074410163339383, 'mean_word_length': 4.429802955665025, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 7, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2003819', 'n_tokens_mistral': 1262, 'n_tokens_neox': 1172, 'n_words': 564}