Skip to main content

Git --CheetSheet=1

1. git help config #shows the usage details of "config"

2. git config --global user.name "yeshsurya"    #add name to configuration

3. git init  #initialize the git repository

4. git status #get the staus of the git repository

5. git add *.html  #add the files using wild card

6. git commit -m "First commit" # make a commit

7. git add css #all the files in directory "css" is added to staging.

8. git log # shows the commit history.

9. git diff HEAD  #difference of the top most commit

10.git diff --staged  #difference of the staged commit

11.git reset ostrich.html #unstage the staged changes

12.git commit -a -m "the commit message" index.html #stage and commit in a single line.

13.git commit --ament -m "will be added to the second commit" #amends last commit by addding files in the staging

14.git reset --soft HEAD^  #undoes the last commit and puts the changes back to staging area.

15.git checkout -- cats.html index.htlm # undo changes on those two files.

16.git reset --hard HEAD^  #undoes the previous commit and discard the changes.

17.git remote add origin git@example.com:example/petshop.git #linking a remote git repository

18.git push -u origin master #-u : remembers the default push branch option.

_________________________________________________



Comments

Popular posts from this blog

Event Sourcing with CQRS.

  The way event sourcing works with CQRS is to have  part of the application that models updates as writes to an event log or Kafka topic . This is paired with an event handler that subscribes to the Kafka topic, transforms the event (as required) and writes the materialized view to a read store.

GraphQL microservices (GQLMS)

I'm curios of GraphQL !     -  GraphQL is an open-source data query and manipulation language for APIs, and a runtime for fulfilling queries with existing data. GraphQL was developed internally by Facebook in 2012 before being publicly released in 2015. It should be solving a problem in querying data !     -GraphQL lets you ask for what you want in a single query, saving bandwidth and reducing waterfall requests. It also enables clients to request their own unique data specifications. A case study ?!    -https://netflixtechblog.com/beyond-rest-1b76f7c20ef6 So, This is just another database technoloy ?  -  No. GraphQL is often confused with being a database technology. This is a misconception, GraphQL is a   query language   for APIs - not databases. In that sense it’s database agnostic and can be used with any kind of database or even no database at all. Source:   howtographql.com