# Create Repository

> Windows | Cross-platform

## Project compatibility

Windows | Cross-platform

## Overview

| Description | API Method | API Path |
| --- | --- | --- |
| The Create Repository activity provisions a new GitHub repository under the authenticated user or organization. | POST | /user/repos |

## Input

| Parameter | Description | Data Type |
| --- | --- | --- |
| Repository name | Name of the repository; not case‑sensitive. | string |
| Description | Short human‑readable description of the repository. | string |
| Private | Whether the repository should be private (`true`) or public (`false`). | boolean |
| Homepage | URL with more information about the repository (for example, project homepage). | string |
| Team ID | ID of a team to grant access to the repository when creating it in an organization. | int32 |
| Auto initialize | Whether to create an initial commit with an empty README. | boolean |
| Allow auto merge | Whether to allow auto‑merge on pull requests. | boolean |
| Delete branch on merge | Whether to automatically delete head branches when pull requests are merged (requires organization owner for enabling in some scenarios). | boolean |
| Template | Whether this repository should be available as a template repository. | boolean |
| Gitignore template | Gitignore template to apply by language or platform name (for example, `Haskell`). | string |
| License template | License template key (for example, `mit`, `mpl-2.0`) to apply an open source license file. | string |
| Has issues | Whether to enable GitHub Issues for this repository. | boolean |
| Visibility | Repository visibility: `public`, `private`, or `internal`. | string |

## Output

| Parameter | Description | Data Type |
| --- | --- | --- |
| Repository ID | Internal ID of the created repository. | int32 |
| Create repository | Full response object for the repository. | Object |

:::note
* In API workflows, a single
response object is returned as the output. Any required fields can be extracted directly from this object.
* In RPA workflows, some output
parameters may differ, but the necessary values can still be retrieved from the response object even if they are not explicitly exposed.
:::