Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: test, adding line on readme file #140

Closed
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 13 additions & 9 deletions README.md
Original file line number Diff line number Diff line change
@@ -1,25 +1,29 @@
# A Git(Hub) Test Repository

Hey! This is my personal Git(Hub) Test Repository where I experiment with Git and GitHub.
|
THANK YOU FOR THIS TEST REPO
|

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:
Hey! This is my personal Git(Hub) Test Repository where I experiment with Git and GitHub.

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.
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:

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

> NOTE
> If you want your PR to have a chance to get merged, please propose additions or changes to neutral files such as text files or small images. If you propose changes to the GitHub workflow files, to `.gitignore`, etc. they will quite probably be rejected.

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.
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 test GitHUb pages (from the `gh-pages` branch) at: http://zpqrtbnk.github.io/test-repo/

We have an image in the README (markdown)
![Image](https://raw.github.com/zpqrtbnk/test-repo/master/wtf.jpg)
Expand All @@ -28,8 +32,8 @@ We have an image in the README (html)
<img src="./wtf.jpg" />

We have an image in the README (more html)

<p align="center" style="background:#000;padding:5px;color:#fff;font-size:150%;margin-bottom:64px">
<img src="./wtf.jpg" />
<span style="margin-left:48px;">wubble</span>
</p>