 Pro Git 2nd Edition 2.1.413and the default password is 5iveL!fe (which you must change right away). After you’ve logged in, click the “Admin area” icon in the menu at the top right. Figure 50. The “Admin area” item in the GitLab what you specify here isn’t permanent, and can be changed later through the settings interface. Click “Create Project”, and you’re done. Once the project exists, you’ll probably want to connect it with finished and you’re ready to contribute it back to the maintainers, go to the original project page and click the “Fork” button, creating your own writable fork of the project. You then need to add this repository0 码力 | 731 页 | 21.49 MB | 1 年前3 Pro Git 2nd Edition 2.1.413and the default password is 5iveL!fe (which you must change right away). After you’ve logged in, click the “Admin area” icon in the menu at the top right. Figure 50. The “Admin area” item in the GitLab what you specify here isn’t permanent, and can be changed later through the settings interface. Click “Create Project”, and you’re done. Once the project exists, you’ll probably want to connect it with finished and you’re ready to contribute it back to the maintainers, go to the original project page and click the “Fork” button, creating your own writable fork of the project. You then need to add this repository0 码力 | 731 页 | 21.49 MB | 1 年前3
 Pro Git 2nd Edition 2.1.413and the default password is 5iveL!fe (which you must change right away). After you’ve logged in, click the “Admin area” icon in the menu at the top right. Figure 50. The “Admin area” item in the GitLab what you specify here isn’t permanent, and can be changed later through the settings interface. Click “Create Project”, and you’re done. 123 Once the project exists, you’ll probably want to connect finished and you’re ready to contribute it back to the maintainers, go to the original project page and click the “Fork” button, creating your own writable fork of the project. You then need to add this repository0 码力 | 501 页 | 17.96 MB | 1 年前3 Pro Git 2nd Edition 2.1.413and the default password is 5iveL!fe (which you must change right away). After you’ve logged in, click the “Admin area” icon in the menu at the top right. Figure 50. The “Admin area” item in the GitLab what you specify here isn’t permanent, and can be changed later through the settings interface. Click “Create Project”, and you’re done. 123 Once the project exists, you’ll probably want to connect finished and you’re ready to contribute it back to the maintainers, go to the original project page and click the “Fork” button, creating your own writable fork of the project. You then need to add this repository0 码力 | 501 页 | 17.96 MB | 1 年前3
 Pro Git 2nd Edition 2.1.413 and the default password is 5iveL!fe (which you must change right away). After you’ve logged in, click the “Admin area” icon in the menu at the top right. Figure 50. The “Admin area” item in the GitLab what you specify here isn’t permanent, and can be changed later through the settings interface. Click “Create Project”, and you’re done. Once the project exists, you’ll probably want to connect it with finished and you’re ready to contribute it back to the maintainers, go to the original project page and click the “Fork” button, creating your own writable fork of the project. You then need to add this repository0 码力 | 691 页 | 13.35 MB | 1 年前3 Pro Git 2nd Edition 2.1.413 and the default password is 5iveL!fe (which you must change right away). After you’ve logged in, click the “Admin area” icon in the menu at the top right. Figure 50. The “Admin area” item in the GitLab what you specify here isn’t permanent, and can be changed later through the settings interface. Click “Create Project”, and you’re done. Once the project exists, you’ll probably want to connect it with finished and you’re ready to contribute it back to the maintainers, go to the original project page and click the “Fork” button, creating your own writable fork of the project. You then need to add this repository0 码力 | 691 页 | 13.35 MB | 1 年前3
 Gitea v1.21.1 中文文档of lines within a file. 1. Navigate to and open the file whose line history you want to view. 2. Click the Blame button in the file header bar. 3. The new view shows the line-by-line revision history a file with author and commit information on the left side. 4. To navigate to an older commit, click the icon. All revisions specified in the .git-blame-ignore-revs file are hidden from the blame0 码力 | 303 页 | 3.88 MB | 1 年前3 Gitea v1.21.1 中文文档of lines within a file. 1. Navigate to and open the file whose line history you want to view. 2. Click the Blame button in the file header bar. 3. The new view shows the line-by-line revision history a file with author and commit information on the left side. 4. To navigate to an older commit, click the icon. All revisions specified in the .git-blame-ignore-revs file are hidden from the blame0 码力 | 303 页 | 3.88 MB | 1 年前3
共 4 条
- 1














