TWS/template
Template
8
0
Fork 0
Code Issues Pull requests 1 Packages Projects Releases Wiki Activity

Compare commits

base: TWS:517503cec353aa1a12a4f1b05ef36470349fa858
Branches Tags
TWS:main
TWS:repo-init
TWS:new
TWS:dummy
..
compare: TWS:a31d4849490dbed263d82c9ceb9fa79176cebbdb
Branches Tags
TWS:repo-init
TWS:new
TWS:dummy
TWS:main

2 commits
517503cec3 ... a31d484949

Author SHA1 Message Date
D. Scott Boggs a31d484949 Add forgotten cd command 2023-09-01 06:21:21 -04:00
D. Scott Boggs d8bc008333 Create empty .gitignore file 2023-09-01 06:20:51 -04:00
2 changed files with 4 additions and 0 deletions
Show stats Expand all files Collapse all files

2
.gitignore vendored
View file

@ -0,0 +1,2 @@
# Add globs to files you don't want tracked to this file. Common examples
# include "**/node_modules", "*.secret", and ".env*".

2
README.md
View file

@ -13,6 +13,8 @@ the top-right of the Forgejo page for the repository. ![Forgejo fork button](htt
$ git clone https://git.tams.tech/{USER}/{REPO}.git $ git clone https://git.tams.tech/{USER}/{REPO}.git
$ # Via SSH: $ # Via SSH:
$ git clone ssh://git@git.tams.tech:2222/{USER}/{REPO}.git $ git clone ssh://git@git.tams.tech:2222/{USER}/{REPO}.git
$ # either way, then do
$ cd {REPO}
``` ```
Note that for private repositories, using HTTPS as the remote means entering Note that for private repositories, using HTTPS as the remote means entering
your credentials at each fetch or push action. Remotes can always be your credentials at each fetch or push action. Remotes can always be