클릭하면 커밋 메시지 텍스트 상자가 확장됩니다. 변경한 내용과 그 이유를 설명하는 커밋 메시지를 작성하십시오. 8. 설정이 올바른지 확인하십시오: Create a new branch를 선택해야 합니다(브 랜치 이름은 다음과 같아야 함: [username]/[very short description of your changes]). 변경을 완료한 다음 변경해야 한다면, 병합 요청 제목 맨 앞에 [WIP]를 붙이 십시오. 5. Allow commits from members who can merge to the target branch. 옵션을 선택 했는지 확인하십시오. 기술적인 이유로 필요합니다. 병합 요청은 master 브 랜치로 리베이스되며, 해당 변경 사항을 기술적으로 변경하지만 실제로 내 용을 변경하지 있습니다. 나중에 더 귀찮은 문제를 피하려면 검토자가 몇 번의 클릭으 로 스스로 할 수 있도록 이 옵션을 선택하는 것이 좋습니다. 6. 대부분의 경우 Delete source branch when merge request is accepted를 선택해 도 무방합니다. 7. 검토자가 달리 말하지 않는 한, Squash commits when merge request

[Ref. QA-1290 and #400] 6.22 Condition End Style 6.22.1 Diamond style (by default) • With one branch @startuml skinparam ConditionEndStyle diamond :A; if (decision) then (yes) :B1; else (no) endif Condition End Style 6 ACTIVITY DIAGRAM (BETA) @enduml 6.22.2 Horizontal line (hline) style • With one branch @startuml skinparam ConditionEndStyle hline :A; if (decision) then (yes) :B1; else (no) endif :C; !include !include !include branch/site_branch.puml> !include !include PlantUML 언어참조가이드

[Ref. QA-1290 and #400] 6.22 Condition End Style 6.22.1 Diamond style (by default) • With one branch @startuml skinparam ConditionEndStyle diamond :A; if (decision) then (yes) :B1; else (no) endif Condition End Style 6 ACTIVITY DIAGRAM (BETA) @enduml 6.22.2 Horizontal line (hline) style • With one branch @startuml skinparam ConditionEndStyle hline :A; if (decision) then (yes) :B1; else (no) endif :C; !include !include !include branch/site_branch.puml> !include !include PlantUML 언어참조가이드

[Ref. QA-1290 and #400] 6.22 Condition End Style 6.22.1 Diamond style (by default) • With one branch @startuml skinparam ConditionEndStyle diamond :A; if (decision) then (yes) :B1; else (no) endif Condition End Style 6 ACTIVITY DIAGRAM (BETA) @enduml 6.22.2 Horizontal line (hline) style • With one branch @startuml skinparam ConditionEndStyle hline :A; if (decision) then (yes) :B1; else (no) endif :C; !include !include !include branch/site_branch.puml> !include !include PlantUML 언어참조가이드

[Ref. QA-1290 and #400] 6.24 Condition End Style 6.24.1 Diamond style (by default) • With one branch @startuml skinparam ConditionEndStyle diamond :A; if (decision) then (yes) :B1; else (no) endif 24 Condition End Style 6 ACTIVITY DIAGRAM (BETA) 6.24.2 Horizontal line (hline) style • With one branch @startuml skinparam ConditionEndStyle hline :A; if (decision) then (yes) :B1; else (no) endif :C; 17.7 Removing box 17 MINDMAP * another first level node <> @endmindmap • Apply style to a branch @startmindmap + root

[Ref. QA-1290 and #400] 5.21 Condition End Style 5.21.1 Diamond style (by default) • With one branch @startuml skinparam ConditionEndStyle diamond :A; if (decision) then (yes) :B1; else (no) endif Style 5 ACTIVITY DIAGRAM (BETA) @enduml @enduml 5.21.2 Horizontal line (hline) style • With one branch @startuml skinparam ConditionEndStyle hline :A; if (decision) then (yes) :B1; else (no) endif :C;

[Ref. QA-1290 and #400] 5.21 Condition End Style 5.21.1 Diamond style (by default) • With one branch @startuml skinparam ConditionEndStyle diamond :A; if (decision) then (yes) :B1; else (no) endif Style 5 ACTIVITY DIAGRAM (BETA) @enduml @enduml 5.21.2 Horizontal line (hline) style • With one branch @startuml skinparam ConditionEndStyle hline :A; if (decision) then (yes) :B1; else (no) endif :C;

크기: {}", size); } 31 Because if is an expression and must have a particular type, both of its branch blocks must have the same type. Show what happens if you add ; after "small" in the second example

크기: {}", size); } 31 Because if is an expression and must have a particular type, both of its branch blocks must have the same type. Show what happens if you add ; after "small" in the second example