donaricano-btn

깃허브(github)로 블로그 만들기


1. 필요 항목

- 깃허브(github) 아이디

- Jekyll github : https://github.com/barryclark/jekyll-now


2. 구성

1) Jekyll 레파지토리에 접근하여 fork 한다

 Jekyll github : https://github.com/barryclark/jekyll-now 에 접속하여 fork 버튼을 클릭한다

- 그럼 아래와 같은 화면이 나타나면서 나의 저장소로 위의 저장소가  fork 된것을 확인 할 수 있다

2)  Page  접근 셋팅

- 셋팅을 클릭합니다

- 자신이 원하는 URL  주소를 설정한다

- 원하는이름.github.io 

- 이제 지정한 주소로 이동하면 아래와 같은 화면을 볼 수 있다


3. 


블로그 이미지

리딩리드

,
donaricano-btn

What if you push the wrong file(dir) to github?


1. Remove

- If you have a wrong file(dir) in your remote repository

1) Move the directory

2) Enter the git command

- git rm -r --cached wrong

- git commit -m "remove a wrong dir"

- git push origin master


'CM(ConfigurationManagement) > github' 카테고리의 다른 글

[GItHub] 깃허브(github)로 블로그 만들기  (0) 2016.12.08
[GitHub] PullRequest Handling  (0) 2016.06.06
[GitHub]How to send a Pull Request  (0) 2016.06.05
[gitHub] Issue  (0) 2016.05.19
[GitHub] 2. Info about github  (0) 2016.05.15
블로그 이미지

리딩리드

,
donaricano-btn

PullRequest Handling


1. Getting a Pull Request


2. How to know the source is safe on origin repository

2_1. Get a sender repository



2_2. To make a topic branch

- Merge

- Check a source 

- Branch delete

I  no longer need a pr1 branch




블로그 이미지

리딩리드

,
donaricano-btn

How to send a Pull Request

- My Code source was copied from other origin repository

- I can send a my changed code to origin repository


1. Pull request flow

1) I've used a open source code and find a bug

2) I fixed a bug and then send a my changed source to origin repository

3) When I send a pull request, The origin repository will be made a issue automatically

4) Manager will  handle it


2. Pull request init

2_1. Fork

- https://github.com/jpub-gh/first-pr 

- fork


2_2. clone

2_3. branch

- Before I develop the clone repository, I have to make a topic branch

- Check a branch

- Making a topic branch


2_4 Add a code


2_5. Commit

git diff

git commit


2_6. Make a remote branch



3. Sending a Pull Request

3_1. Change a branch and Check


3_2. Create pull request


4. Beyond Pull request

4_1. To send a pull request for discussion during developing

- Suggest a new function 

- Advice

- etc..


4_2. How to  inform us of status of developing

- To prevent a wrong merge during developing, I can attach a [WIP](work in progress) in my request source


5. Manage repository

- How to maintain latest status of my forked repository


5_1. Fork, clone


5_2. configure repository name


5_3. Get latest data


 







'CM(ConfigurationManagement) > github' 카테고리의 다른 글

[GitHub] What if you push the wrong file(dir) to github?  (0) 2016.08.25
[GitHub] PullRequest Handling  (0) 2016.06.06
[gitHub] Issue  (0) 2016.05.19
[GitHub] 2. Info about github  (0) 2016.05.15
[GitHub] 1. SSH Key  (0) 2016.05.08
블로그 이미지

리딩리드

,