kamikaze/test-repo-new-commits
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Stephan 2021-10-24 17:32:09 +02:00 committed by GitHub
parent 0d7242e7fc
commit 6285473aa7
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
README.md
View File

@ -2,11 +2,17 @@
Hey! This is my personal Git(Hub) Test Repository where I experiment with Git and GitHub.
If you are new to Git and GitHub and found this repository through Google: feel free to clone the repository and experiment with it! You will not be able to push back to the repository, as it is *my* repository and I cannot let everybody push to it. The right way to do it on GitHub is: (1) fork the repository in your own account, (2) make changes and push them in a branch of your own fork, (3) create a Pull Request in my repository. I will get notified, will review the changes that you propose, and eventually will either merge the changes, or reject them. This *may* take some time as I am not actively monitoring nor maintaining this repository, as you can guess, but I try to be helpful ;)
If you are new to Git and GitHub and found this repository through Google: feel free to clone the repository and experiment with it! You will not be able to push back to the repository, as it is *my* repository and I cannot let everybody push to it. The right way to do it on GitHub is:
Don't expect to find anything meaningful nor useful in the repository. Also, I happen to force-push a reset of everything from time to time. This means that I reset all history, including changes that you may have submitted. Hey, this is a *test* repository after all.
1. fork the repository in your own account,
2. make changes and push them in a branch of your own fork,
3. create a Pull Request in my repository.
The rest of this README file is
I will get notified, will review the changes that you propose, and eventually will either merge the changes, or reject them. This *may* take some time as I am not actively monitoring nor maintaining this repository, as you can guess, but I try to be helpful ;)
Don't expect to find anything meaningful nor useful in the repository. Also, I happen to force-push a reset of everything from time to time. This means that I reset all history, including changes that you may have submitted. In theory, noone ever does this to a repository. But hey, this is a *test* repository after all.
The rest of this README file is mostly random stuff.
Clone the repository with: `git clone https://github.com/zpqrtbnk/test-repo.git .`