Administration Managing an organization Organization Basics Teams Audit Log Scripting GitHub Services and Hooks The GitHub API Basic Usage Commenting on an Issue Changing the Status of a Pull Request existing Git repository from elsewhere. In either case, you end up with a Git repository on your local machine, ready for work. Initializing a Repository in an Existing Directory If you have a project directory Changes to the Repository At this point, you should have a bona fide Git repository on your local machine, and a checkout or working copy of all of its files in front of you. Typically, you’ll want to start

Administration Managing an organization Organization Basics Teams Audit Log Scripting GitHub Services and Hooks The GitHub API Basic Usage Commenting on an Issue Changing the Status of a Pull Request existing Git repository from elsewhere. In either case, you end up with a Git repository on your local machine, ready for work. Initializing a Repository in an Existing Directory If you have a project directory Changes to the Repository At this point, you should have a bona fide Git repository on your local machine, and a checkout or working copy of all of its files in front of you. Typically, you’ll want to start

existing Git repository from elsewhere. In either case, you end up with a Git repository on your local machine, ready for work. Initializing a Repository in an Existing Directory If you have a project directory Changes to the Repository At this point, you should have a bona fide Git repository on your local machine, and a checkout or working copy of all of its files in front of you. Typically, you’ll want to start specify your own log output format. This is especially useful when you’re generating output for machine parsing — because you specify the format explicitly, you know it won’t change with updates to Git:

让我们看看当两个开发者在一个共享仓库中一起工作时会是 什么样子。 第一个开发者，John，克隆了仓库，做了改动，然后本地提交。 （为了缩短这些例子长度，协议信 息已被替换为 …。） # John's Machine $ git clone john@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim lib/simplegit files changed, 1 insertions(+), 1 deletions(-) 第二个开发者，Jessica，做了同样的事情——克隆仓库并提交了一个改动： # Jessica's Machine $ git clone jessica@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim TODO task 1 files changed, 1 insertions(+), 0 deletions(-) 现在，Jessica 把她的工作推送到服务器上，一切正常： # Jessica's Machine $ git push origin master ... To jessica@githost:simplegit.git 1edee6b..fbff5bc master -> master

让我们看看当两个开发者在一个 共享仓库中一起工作时会是什么样子。 第一个开发者，John，克隆了仓库， 做了改动，然后本地提交。 （为了缩短这些例子长度，协议信息已被替换为 … 。） # John's Machine $ git clone john@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim lib/simplegit files changed, 1 insertions(+), 1 deletions(-) 第二个开发者，Jessica，做了同样的事情——克隆仓库并提交了一个改动： # Jessica's Machine $ git clone jessica@githost:simplegit.git Cloning into 'simplegit'... ... $ cd simplegit/ $ vim TODO task 1 files changed, 1 insertions(+), 0 deletions(-) 现在，Jessica 把她的工作推送到服务器上，一切正常： # Jessica's Machine $ git push origin master ... To jessica@githost:simplegit.git 1edee6b..fbff5bc master -> master

--config \"C:\gitea\custom\conf\app.ini\"" 别忘了将 C:\gitea 替换成你的 Gitea 安装目录。 之后在控制面板打开 “Windows Services”，搜索 “gitea”，右键选择 “Run”。在浏览器打开 http://localhost:3000 就可以访问了。（如果你修改了端口，请访问对应的端口，3000是默认端口）。 要将启动依赖项添加到 3. touch docker-compose.yml 然后将以下内容粘贴到名为 docker-compose.yml 的文件中： 1. version: "2" 2. 3. services: 4. server: 5. image: gitea/gitea:1.21.1-rootless 6. restart: always 7. volumes: 16-dev-rootless ）。 要将集成的SSH和Web服务器绑定到不同的端口，请调整端口部分。通常只需更改主机端口并保持容器内的端口不变。 1. version: "2" 2. 3. services: 4. server: 5. image: gitea/gitea:1.21.1-rootless 6. restart: always 7. volumes: