8000 Added Repository templates section · phiberoptick/github-cheat-sheet@ad15b71 · GitHub
[go: up one dir, main page]

Skip to content

Commit ad15b71

Browse files
authored
Added Repository templates section
New feature that allows a repository to be used as a template
1 parent 27749b9 commit ad15b71

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

README.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -76,6 +76,7 @@ A collection of cool hidden and not so hidden features of Git and GitHub. This c
7676
- [Git Books](#git-books)
7777
- [Git Videos](#git-videos)
7878
- [Git Articles](#git-articles)
79+
-[Repository Templates](#repository-templates)
7980

8081
## GitHub
8182
### Ignore Whitespace
@@ -669,6 +670,19 @@ e.g. [https://github.com/tiimgreen.keys](https://github.com/tiimgreen.keys)
669670

670671
[*Read more about accessing public ssh keys.*](https://changelog.com/github-exposes-public-ssh-keys-for-its-users/)
671672

673+
### Repository Templates
674+
675+
You can set your repository to template which allows anyone to copy the files and structure and allowing them to instantly use the files (e.g. for a tutorial or if writing boilerplate code).
676+
677+
This is done by going into settings for your repository and changing it to a template one
678+
![Convert](https://i.postimg.cc/hGCrVm9F/Template.gif)
679+
680+
Changing to a template repository will give a new URL endpoint which can be shared and instantly allows users to use your repository as a template. Alternatively, they can go to your repository and click the 'Use as template' button.
681+
682+
![Template](https://i.postimg.cc/L8PKCHx0/New-Template.gif)
683+
684+
[*Read more about using repositories as templates*](https://github.blog/2019-06-06-generate-new-repositories-with-repository-templates/)
685+
672686
## Git
673687
### Remove All Deleted Files from the Working Tree
674688
When you delete a lot of files using `/bin/rm` you can use the following command to remove them from the working tree and from the index, eliminating the need to remove each one individually:

0 commit comments

Comments
 (0)
0