mirror of
https://codeberg.org/forgejo/forgejo.git
synced 2024-11-14 14:06:15 +01:00
bd4c7ce578
This PR cleans up the docs in a way to make them simpler to ingest by our [docs repo](https://gitea.com/gitea/gitea-docusaurus). 1. It includes all of the sed invocations our ingestion did, removing the need to do it at build time. 2. It replaces the shortcode variable replacement method with `@variable@` style, simply for easier sed invocations when required. 3. It removes unused files and moves the docs up a level as cleanup. --------- Signed-off-by: jolheiser <john.olheiser@gmail.com>
70 lines
2.4 KiB
Markdown
70 lines
2.4 KiB
Markdown
---
|
|
date: "2020-07-06T16:00:00+02:00"
|
|
title: "Push"
|
|
slug: "push"
|
|
sidebar_position: 15
|
|
toc: false
|
|
draft: false
|
|
aliases:
|
|
- /en-us/push-to-create
|
|
- /en-us/push-options
|
|
menu:
|
|
sidebar:
|
|
parent: "usage"
|
|
name: "Push"
|
|
sidebar_position: 15
|
|
identifier: "push"
|
|
---
|
|
|
|
There are some additional features when pushing commits to Gitea server.
|
|
|
|
# Open PR through Push
|
|
|
|
When you push commits to a non-default branch for the first time,
|
|
you will receive a link you can click on to visit the compare page of your branch compared to your main branch.
|
|
From there, it's easy to create a pull request, even if you want to target another branch.
|
|
|
|
|
|
|
|
# Push Options
|
|
|
|
In Gitea `1.13`, support for some [push options](https://git-scm.com/docs/git-push#Documentation/git-push.txt--oltoptiongt)
|
|
were added.
|
|
|
|
## Supported Options
|
|
|
|
- `repo.private` (true|false) - Change the repository's visibility.
|
|
|
|
This is particularly useful when combined with push-to-create.
|
|
|
|
- `repo.template` (true|false) - Change whether the repository is a template.
|
|
|
|
Example of changing a repository's visibility to public:
|
|
|
|
```shell
|
|
git push -o repo.private=false -u origin main
|
|
```
|
|
|
|
# Push To Create
|
|
|
|
Push to create is a feature that allows you to push to a repository that does not exist yet in Gitea. This is useful for automation and for allowing users to create repositories without having to go through the web interface. This feature is disabled by default.
|
|
|
|
## Enabling Push To Create
|
|
|
|
In the `app.ini` file, set `ENABLE_PUSH_CREATE_USER` to `true` and `ENABLE_PUSH_CREATE_ORG` to `true` if you want to allow users to create repositories in their own user account and in organizations they are a member of respectively. Restart Gitea for the changes to take effect. You can read more about these two options in the [Configuration Cheat Sheet](administration/config-cheat-sheet.md#repository-repository).
|
|
|
|
## Using Push To Create
|
|
|
|
Assuming you have a git repository in the current directory, you can push to a repository that does not exist yet in Gitea by running the following command:
|
|
|
|
```shell
|
|
# Add the remote you want to push to
|
|
git remote add origin git@{domain}:{username}/{repo name that does not exist yet}.git
|
|
|
|
# push to the remote
|
|
git push -u origin main
|
|
```
|
|
|
|
This assumes you are using an SSH remote, but you can also use HTTPS remotes as well.
|
|
|
|
Push-to-create will default to the visibility defined by `DEFAULT_PUSH_CREATE_PRIVATE` in `app.ini`.
|