bb25f85ce8
This was intended to be a small followup for https://github.com/go-gitea/gitea/pull/23712, but...here we are. 1. Our docs currently use `slug` as the entire URL, which makes refactoring tricky (see https://github.com/go-gitea/gitea/pull/23712). Instead, this PR attempts to make future refactoring easier by using slugs as an extension of the section. (Hugo terminology) - What the above boils down to is this PR attempts to use directory organization as URL management. e.g. `usage/comparison.en-us.md` -> `en-us/usage/comparison/`, `usage/packages/overview.en-us.md` -> `en-us/usage/packages/overview/` - Technically we could even remove `slug`, as Hugo defaults to using filename, however at least with this PR it means `slug` only needs to be the name for the **current file** rather than an entire URL 2. This PR adds appropriate aliases (redirects) for pages, so anything on the internet that links to our docs should hopefully not break. 3. A minor nit I've had for a while, renaming `seek-help` to `support`. It's a minor thing, but `seek-help` has a strange connotation to it. 4. The commits are split such that you can review the first which is the "actual" change, and the second is added redirects so that the first doesn't break links elsewhere. --------- Signed-off-by: jolheiser <john.olheiser@gmail.com>
72 lines
2.3 KiB
Markdown
72 lines
2.3 KiB
Markdown
---
|
|
date: "2020-07-06T16:00:00+02:00"
|
|
title: "使用: Push"
|
|
slug: "push"
|
|
weight: 15
|
|
toc: false
|
|
draft: false
|
|
aliases:
|
|
- /zh-tw/push-options
|
|
menu:
|
|
sidebar:
|
|
parent: "usage"
|
|
name: "Push"
|
|
weight: 15
|
|
identifier: "push"
|
|
---
|
|
|
|
**Table of Contents**
|
|
|
|
{{< toc >}}
|
|
|
|
There are some additional features when pushing commits to Gitea server.
|
|
|
|
# Push Merge Hint
|
|
|
|
When you pushing commits to a non-default branch, you will get an information from
|
|
Gitea which is a link, you can click the link and go to a compare page. It's a quick
|
|
way to create a pull request or a code review yourself in the Gitea UI.
|
|
|
|
|
|
|
|
# Push Options
|
|
|
|
Gitea 從 `1.13` 版開始支援某些 [push options](https://git-scm.com/docs/git-push#Documentation/git-push.txt--oltoptiongt)
|
|
。
|
|
|
|
## 支援的 Options
|
|
|
|
- `repo.private` (true|false) - 修改儲存庫的可見性。
|
|
|
|
與 push-to-create 一起使用時特別有用。
|
|
|
|
- `repo.template` (true|false) - 修改儲存庫是否為範本儲存庫。
|
|
|
|
以下範例修改儲存庫的可見性為公開：
|
|
|
|
```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]({{< relref "doc/administration/config-cheat-sheet.zh-tw.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.
|