need to review docs

[nhn]

need to review docs

[SetCodesToFire]

Hi I want to help you in this. Can i contribute?

[kyuwoo-choi]

@SetCodesToFire Sure! go ahead and give me a PR 😄
just make sure you're working on master branch

[SetCodesToFire]

Hi.. What I usually do is

1. fork the repository
2. clone it in my local hard drive
3. switch the branch
4. do the significant chances in the repo
5. add,commit
6. push to origin branch-name

I did these steps in this repo too but i am left with an error thrown on the console saying that i am behind the master branch. Can you tell me how to overcome this. Thank You. 👍

[kyuwoo-choi]

Hey @SetCodesToFire I think you need to follow https://help.github.com/articles/syncing-a-fork/
Cheers!

[SetCodesToFire]

Hi @kyuwoo-choi thank you so much.

[SetCodesToFire]

@kyuwoo-choi I am still facing issues. What could be done ,can you please help. I cannot get how to work on your master branch. I have forked the repo, then cloned it in my local drive, then i am doing git checkout -b master, which switches me to master branch, then i did the necessary changes and at last git checkout and git push origin master.

But when i am trying to push it,an error is shown on the screen telling that the files that i have cloned is some commits before the master branch,to push the file ,first i have to make a pull.

Is there a work around in this like i have to first clone the repo and then pull your master branch?

[kyuwoo-choi]

hey @SetCodesToFire

git checkout -b master won't do anything because what it does is creating a new branch named master which is already exist.
git checkout master will switch to master which is you'll want.

and you can not push to this repo directory. it's locked.

I see you have a commit in production branch in your repo.
So this time, just try again without -b when you switch the branch to master.

Thanks for your effort 👍

[SetCodesToFire]

Finally did it. 👍 Thank you so much for appreciating me @kyuwoo-choi .