https://github.com/jaronoff97/githubtests

This is a test for people to learn how to use github, we're going to be learning how to push, pull, and branch a git repo
https://github.com/jaronoff97/githubtests

Last synced: 8 days ago
JSON representation

This is a test for people to learn how to use github, we're going to be learning how to push, pull, and branch a git repo

• Host: GitHub
• URL: https://github.com/jaronoff97/githubtests
• Owner: jaronoff97
• License: apache-2.0
• Created: 2015-10-16T15:55:35.000Z (about 9 years ago)
• Default Branch: master
• Last Pushed: 2015-10-23T16:39:42.000Z (about 9 years ago)
• Last Synced: 2024-10-28T15:48:44.368Z (about 2 months ago)
• Language: Java
• Size: 156 KB
• Stars: 1
• Watchers: 3
• Forks: 7
• Open Issues: 0
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# GitHubTests

This is a test for people to learn how to use github, we're going to be learning how to push, pull, and branch a git repo

To put your project up on GitHub, you'll need a repository for it to live in. Let's create one!


On GitHub, you can store all kinds of projects in repositories. Personal repositories belong to user accounts, so after you've signed up for GitHub, you can create your first repository!




Create a new repository on GitHub




In the upper-right corner of any page, click , and then click New repository.

Create a short, memorable name for your repository. For example, "hello-world".

Optionally, add a description of your repository. For example, "My first repository on GitHub."



Choose between creating a public or private repository.






Public repositories are a great choice for getting started! They're visible to any user on GitHub, so you can benefit from a collaborative community.



Private repositories require a little more setup. They're only available to you, the repository owner, as well as any collaborators you choose to share with. Private repositories are only available for paid accounts. For more information, see "What plan should I choose?."







Select Initialize this repository with a README.



Click Create repository.





Congratulations! You've successfully created your first repository, and initialized it with a README file.




Commit your first change


A commit is like a snapshot of all the files in your project at a particular point in time.


When you created your new repository, you initialized it with a README file. README files are a great place to describe your project in more detail, or add some documentation such as how to install or use your project. The contents of your README file are automatically shown on the front page of your repository.


Let's commit a change to the README file.




In your repository's list of files, click README.md.



Above the file's content, click .

On the Edit file tab

, type some information about yourself.



Above the new content, click Preview changes.

Review the changes you made to the file. You'll see the new content in green.

At the bottom of the page, type a short, meaningful commit message that describes the change you made to the file.

Below the commit message fields, decide whether to add your commit to the current branch or to a new branch. If your current branch is master, you should choose to create a new branch for your commit and then create a pull request.

Click Propose file change.





Celebrate


Congratulations! You have now created a repository, including a README file, and created your first commit on GitHub. What do you want to do next?