kamikaze/test-repo-different-tags
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Test repo, with same tag (meh) pointing to different commit and v tag renamed to vv.
151 Commits 20 Branches 13 Tags 388 KiB
JavaScript 100%
3356fe58aa
Go to file
Stephan 3356fe58aa fix
2021-12-16 12:49:06 +01:00
.github fix 2021-12-16 12:49:06 +01:00
duh bah 2021-10-20 09:05:22 +02:00
.gitignore embed 2021-06-14 17:24:55 +02:00
6.txt Update 6.txt 2021-12-12 23:35:15 +02:00
bang created symlink 2021-10-20 07:17:10 +00:00
dan.txt A non-conflicting change 2021-10-23 12:18:09 -04:00
duh.txt duh 2021-12-03 11:13:42 +01:00
e.txt Merge branch 'dnew' - fixed conflict manually in 'vim' 2021-10-23 12:21:34 -04:00
foo.txt Foo 2021-12-03 10:11:00 +00:00
README.md Update README.md 2021-10-24 17:32:09 +02:00
test.txt Add files via upload 2021-12-12 03:51:28 +02:00
wtf.jpg add image 2012-11-21 16:26:37 +01:00

README.md

A Git(Hub) Test Repository

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 ;)

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 .

We have test GitHUb pages (from the gh-pages branch) at: http://zpqrtbnk.github.io/test-repo/

We have an image in the README (markdown) Image

We have an image in the README (html)

We have an image in the README (more html)

wubble