'CM(ConfigurationManagement)'에 해당되는 글 12건

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

 Issue

- Bug or discussion about development

- Issue is managed by BTS(Bug Tracking System)

1. When do we use ?

- Find a bug

- Counsel or question

- Function that will be added

2. Syntax Highlight

````ruby

def hello_world

puts 'hello'

end

````

3. How to handle the issues

3_1. Label

- Attach a Label to the issue

3_2. milestones

- Use Milestones to create collections of Issues and Pull Requests for a particular release or project.

4. To do list

5. Control Issue by using commit

5_1. commit to relate to issue

- Issues has a own number like #1

- I commit with issue number 

5_2. Issue will be closed 

- Example : commit message + fix #1

close #1

resolve #1.. etc

Info about github

1. shortcut key

shift + /

2. How to check a content change

- branch...branch

2_1. To check a content change during 7 days

- compare/master@{7.day.ago}...master

- day, week, month, year

2_2. To check a content change from specific day

- compare/master@{2015-01-01}...master

Remote config

1. git remote add    

- git remote identifier is origin

2. git push

2_1. transmission from master

 -u

local branch's upstream will be set up as a origin(remote)'s master branch

so when you execute a pull command, you can get a master branch on the remote repository

2_2. transmission from others

3. git clone

3_1. To get a remote repository

3_2. remote's branch feature-D How to checkout

- git checkout -b feature-D

(Create a branch's feature-D)

- origin/feature-D

(reference to remote branch's feature-D)

3_3 Commit as a feature_D

3_4 To push to feature-D

3_5. git pull