Git Product home page Git Product logo

hacktoberfest's Introduction

HacktoberFest-NITK

Here is a basic outline of how to write Git instructions in the repository!

Tell Git who you are Configure the author name and email address to be used with your commits.

Note that Git strips some characters (for example trailing periods) from user.name.

$ git config --global user.name "Salman Shah"

$ git config --global user.email [email protected]

Create a new local repository

$ git init

Check out a repository

Create a working copy of a local repository:

$ git clone /path/to/repository

For a remote server, use:

$ git clone username@host:/path/to/repository

Add files

Add one or more files to staging (index):

$ git add <filename>

Add all files to staging area:

$ git add --all

Commit

Commit changes to head (but not yet to the remote repository):

$ git commit -m "Commit message"

Commit any files you've added with git add, and also commit any files you've changed since then:

$ git commit -a

Push

Send changes to the master branch of your remote repository:

$ git push origin master

Status List the files you've changed and those you still need to add or commit:

$ git status

Connect to a remote repository

If you haven't connected your local repository to a remote server, add the server to be able to push to it:

$ git remote add origin <server>

List all currently configured remote repositories:

$ git remote -v

Branches

Create a new branch and switch to it:

$ git checkout -b <branchname>

Switch from one branch to another:

$ git checkout <branchname>

List all the branches in your repo, and also tell you what branch you're currently in:

$ git branch

Delete the feature branch:

$ git branch -d <branchname>

Delete branch from GitHub

$ git push origin <branchname> --delete

Push the branch to your remote repository, so others can use it:

$ git push origin <branchname>

Push all branches to your remote repository:

$ git push --all origin

Delete a branch on your remote repository:

$ git push origin :<branchname>

Update from the remote repository Fetch and merge changes on the remote server to your working directory:

$ git pull

To merge a different branch into your active branch:

$ git merge <branchname>

View all the merge conflicts:

View the conflicts against the base file:

Preview changes, before merging:

$ git diff


$ git diff --base <filename>

$ git diff <sourcebranch> <targetbranch>

After you have manually resolved any conflicts, you mark the changed file:

$ git add <filename>

Remotes

Remotes are useful for tracking repositories which are present on multiple Git servers(such as Github, Bitbucket, etc.) You can add multiple remote URLs

$ git remote add upstream <url>

Similarly, you can remove added remotes, such as:

$ git remote remove upstream

Undo local changes

If you mess up, you can replace the changes in your working tree with the last content in head:

Changes already added to the index, as well as new files, will be kept.

$ git checkout -- <filename>

Instead, to drop all your local changes and commits, fetch the latest history from the server and point your local master branch at it, do this:

$ git fetch origin

$ git reset --hard origin/master

hacktoberfest's People

Contributors

aditigupta17 avatar aneesh297 avatar arunraj97 avatar aryanhimanshu avatar awadhesh1994 avatar awadhesh31 avatar ayush113 avatar chinmaydd avatar dcunhaj avatar djarpit avatar himadrip avatar khursheedali38 avatar man007yadav avatar manishsbhoopalam avatar mayanktripathi01 avatar nachiketun avatar namrata7199 avatar pankajc007 avatar psushaanth23 avatar rawat31 avatar rohitkyadav avatar satan11 avatar sbshah97 avatar shiva1208 avatar shubham35github avatar smarty1palak avatar sujaydcss avatar surajk1509 avatar tr0nand avatar vilas897 avatar

Stargazers

 avatar

Watchers

 avatar  avatar  avatar  avatar  avatar

hacktoberfest's Issues

Add Documentation for Bubble Sort

Explain the basic concept of the Algorithm in the README.md file in the folder!

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Add Binary Search in C

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Add Linear Search in C

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Add Selection Sort in C

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Add MIT License

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Add 'Hello World' in Ruby

Note:
This is an admin-only Issue used only for demonstration! Do not claim this Issue. Your PR for this will not be accepted at any costs!

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Add Documentation for Binary Search

Explain the basic concept of the Algorithm in the README.md file in the folder!

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Add Bubble Sort Algorithm

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Add Hello World in C++

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Add Documentation for Selection Sort

Explain the basic concept of the Algorithm in the README.md file in the folder!

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Add Hello World in Java

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Add Hello World in C

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Add Documentation for Linear Search

Explain the basic concept of the Algorithm in the README.md file in the folder!

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Add CONTRIBUTING.md

Click on the link here to see an example.

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Add Standard format for README

Example README link can be found here

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Create a Menu Based Calculator which takes input from the User

All languages are welcome here! Make sure you reference the Issue!
You have to create a menu-driven calculator which asks the user for the two inputs and the operand symbol. Include addition, division, multiplication and division!

Ground rules:

  1. Whoever claims the Issue first, should send a Pull Request within 24 hours else it'll be assigned to another claimant and further Pull Requests regarding that issue will not be entertained.
  2. Pull Requests sent without claiming and referencing the Issue will not be entertained.
  3. Make sure your Pull Requests have just one commit in them. Squash multiple commits into one if you have to.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.