Resources.md

Hacktoberfest® is open to everyone in our global community. Whether you’re a seasoned contributor or looking for projects to contribute to for the first time, you’re welcome to participate.

Visit Hacktoberfest Website to know more.

How to register:

• Go to https://github.com & create an account.
• Then register at https://hacktoberfest.digitalocean.com/register by logging through your GitHub Account and you're all set to contribute for Hacktoberfest.

But there are some rules for Hacktoberfest and here we go:

✅ Pull requests can be submitted to any opted-in repository on GitHub or GitLab.

✅ The pull request must contain commits you made yourself.

⚠️ If a maintainer reports your pull request as spam, it will not be counted toward your participation in Hacktoberfest.

⚠️ If a maintainer reports behavior that’s not in line with the project’s code of conduct, you will be ineligible to participate.

✅ To get a shirt, you must make four approved pull requests (PRs) on opted-in projects between October 1-31 in any time zone.

😀 This year, the first 50,000 participants can earn a T-shirt.

A repository/project is considered to be participating in Hacktoberfest if the 'hacktoberfest' topic is present and is accepting public contributions via pull requests. An individual pull request can also be opted-in directly by adding the 'hacktoberfest-accepted' label.

A pull request is considered approved once it has an overall approving review from maintainers, or has been merged by maintainers, or has been given the 'hacktoberfest-accepted' label. A pull request with any label containing the word 'spam' or 'invalid' will be considered ineligible for Hacktoberfest.

Read the participation details to learn how to earn your Hacktoberfest tee or tree reward.

Resources for learning Git and GitHub

What is Git?

Git is a Distributed Version Control System. If you didn't understand anything then read this blog.

What is GitHub?

GitHub is a code hosting platform for version control and collaboration. It lets you and others work together on projects from anywhere.

Here we provide some resources for learning Git and GitHub from beginner to advanced level.

All the resources are free.

Video Resources

• Git Started with GitHub(Udemy)

• Intro to Git(Udemy)

• Git: Become an Expert in Git & GitHub in 4 Hours(Udemy)

• Git and GitHub - Step by Step for Beginners(Udemy)

• Version Control with Git(Coursera)

• Git and GitHub for Beginners - Crash Course(YouTube - freeCodeCamp.org)

Text Resources

• Deep Dive Into Git

• Learn Git Branching

• git - the simple guide

• Learn Git with Bitbucket Cloud

Cheatsheets

• Git cheat sheet(Atlassian)

• Git cheat sheet(GitHub Education)

• Git cheat sheet(GitHub Training)

• Git cheat sheet(Git Tower)

• Git cheat sheet

• Git cheat sheet(UCSD DSE MAS)

How to Participate

1. Fork the Repo

   Give a start and ⭐ Click on fork button in the right corner.It will create a copy of repositiry in your account.

   • Check here How to fork

   • Image:

     

2. Clone the Repo

   You can clone your repository in your local pc with use of GitHub Desktop application or for your Terminal/bash.

   For Terminal -

   git clone <url_name>

   • Cloning the Repository

   • Image:

     
     

3. Upload your Code or Change and Push it

   

   After doing necessary edits run commands:

   • git add .

     • This command updates the index using the current content found in the working tree, to prepare the content staged for the next commit. It typically adds the current content of existing paths as a whole, but with some options it can also be used to add content with only part of the changes made to the working tree files applied, or remove paths that do not exist in the working tree anymore.

     • The "index" holds a snapshot of the content of the working tree, and it is this snapshot that is taken as the contents of the next commit. Thus after making any changes to the working tree, and before running the commit command, you must use the add command to add any new or modified files to the index.

     • This command can be performed multiple times before a commit. It only adds the content of the specified file(s) at the time the add command is run; if you want subsequent changes included in the next commit, then you must run git add again to add the new content to the index.

     • The git status command can be used to obtain a summary of which files have changes that are staged for the next commit.

     • The git add command will not add ignored files by default. If any ignored files were explicitly specified on the command line, git add will fail with a list of ignored files. Ignored files reached by directory recursion or filename globbing performed by Git (quote your globs before the shell) will be silently ignored. The git add command can be used to add ignored files with the -f (force) option.

   • git status

     • Displays paths that have differences between the index file and the current HEAD commit, paths that have differences between the working tree and the index file, and paths in the working tree that are not tracked by Git (and are not ignored by gitignore). The first are what you would commit by running git commit; the second and third are what you could commit by running git add before running git commit.

   • git commit -m "<your message>" (exclude brackets)

     • Takes the staged snapshot and commits it to the project history. Combined with git add, this defines the basic workflow for all Git users.

   • git remote add origin <url> (exclude brackets)

     • When you clone a repository with git clone , it automatically creates a remote connection called origin pointing back to the cloned repository. This is useful for developers creating a local copy of a central repository, since it provides an easy way to pull upstream changes or publish local commits.

   • git push --force origin master

     • Updates remote refs using local refs, while sending objects necessary to complete the given refs.

     • You can make interesting things happen to a repository every time you push into it, by setting up hooks there.

     • Push your first code

4. Make a PR

   Now Since you're done with pushing your code. It's time to do that thing for which we are actually waiting & that is PULL REQUEST (in short PR).

   • Tap Pull request
   
   • Tap Create pull request
   
   • Write the Title & Description & Tap Create pull request
   
   • Pull requests let you tell others about changes you've pushed to a GitHub repository. Once a pull request is sent, interested parties can review the set of changes, discuss potential modifications, and even push follow-up commits if necessary.

🚀 Voila! You have Contributed to Open-Source 😋.

If you stuck somewhere, contact here.