Skip to content

Conversation

@doyeonk429
Copy link
Member

@doyeonk429 doyeonk429 commented Oct 1, 2025

πŸ”— κ΄€λ ¨ 이슈

  • Close #

πŸ“˜ μž‘μ—… μœ ν˜•

  • ✨ Feature (κΈ°λŠ₯ μΆ”κ°€)
  • 🐞 Bugfix (버그 μˆ˜μ •)
  • πŸ”§ Refactor (μ½”λ“œ λ¦¬νŒ©ν† λ§)
  • βš™οΈ Chore (ν™˜κ²½ μ„€μ •)
  • πŸ“ Docs (λ¬Έμ„œ μž‘μ„± 및 μˆ˜μ •)
  • βœ… Test (κΈ°λŠ₯ ν…ŒμŠ€νŠΈ)
  • 🎨 style (μ½”λ“œ μŠ€νƒ€μΌ μˆ˜μ •)

πŸ“™ μž‘μ—… λ‚΄μ—­

πŸ§ͺ ν…ŒμŠ€νŠΈ λ‚΄μ—­

  • λΈŒλΌμš°μ €/κΈ°κΈ°μ—μ„œ λ™μž‘ 확인
  • μ—£μ§€ μΌ€μ΄μŠ€ ν…ŒμŠ€νŠΈ μ™„λ£Œ
  • κΈ°μ‘΄ κΈ°λŠ₯ 영ν–₯ μ—†μŒ

🎨 μŠ€ν¬λ¦°μƒ· λ˜λŠ” μ‹œμ—° μ˜μƒ (선택)

κΈ°λŠ₯ 미리보기 κΈ°λŠ₯ 미리보기
κΈ°λŠ₯ μ„€λͺ… κΈ°λŠ₯ μ„€λͺ…

βœ… PR 체크리슀트

  • 컀밋 λ©”μ‹œμ§€κ°€ λͺ…ν™•ν•©λ‹ˆλ‹€
  • PR 제λͺ©μ΄ μ»¨λ²€μ…˜μ— λ§žμŠ΅λ‹ˆλ‹€
  • κ΄€λ ¨ 이슈 번호λ₯Ό μž‘μ„±ν–ˆμŠ΅λ‹ˆλ‹€
  • κΈ°λŠ₯이 μ •μƒμ μœΌλ‘œ μž‘λ™ν•©λ‹ˆλ‹€
  • λΆˆν•„μš”ν•œ μ½”λ“œλ₯Ό μ œκ±°ν–ˆμŠ΅λ‹ˆλ‹€

πŸ’¬ μΆ”κ°€ μ„€λͺ… or 리뷰 포인트 (선택)

  • ..

Summary by CodeRabbit

  • μž‘μ—…(Chores)
    • Jira 연동 μ›Œν¬ν”Œλ‘œμš°λ₯Ό μ—…λ°μ΄νŠΈν•˜μ—¬ μžλ™ 생성 이슈의 κΈ°λ³Έ νƒ€μž…μ„ Sub-task둜 μ„€μ •ν–ˆμŠ΅λ‹ˆλ‹€. λ‹€λ₯Έ ν•„λ“œλ‚˜ 단계, μ—λŸ¬ 처리 λ‘œμ§μ—λŠ” 변경이 μ—†μŠ΅λ‹ˆλ‹€. λ°°ν¬λ‚˜ μ• ν”Œλ¦¬μΌ€μ΄μ…˜ κΈ°λŠ₯μ—λŠ” 영ν–₯이 μ—†μœΌλ©°, μ΅œμ’… μ‚¬μš©μž κ²½ν—˜ 변화도 μ—†μŠ΅λ‹ˆλ‹€. λ‚΄λΆ€ 이슈 νŠΈλž˜ν‚Ήμ˜ 일관성을 μœ μ§€ν•˜λ©° 개발 ν”„λ‘œμ„ΈμŠ€ μžλ™ν™” μ•ˆμ •μ„±μ€ κΈ°μ‘΄κ³Ό λ™μΌν•©λ‹ˆλ‹€.

@coderabbitai
Copy link

coderabbitai bot commented Oct 1, 2025

Walkthrough

Jira 이슈 생성 μ›Œν¬ν”Œλ‘œμš°μ—μ„œ μƒμ„±λ˜λŠ” 이슈 νƒ€μž…μ„ Taskμ—μ„œ SubTask둜 λ³€κ²½ν–ˆμŠ΅λ‹ˆλ‹€. λ‹€λ₯Έ ν•„λ“œλ‚˜ 처리 흐름은 λ³€κ²½λ˜μ§€ μ•Šμ•˜μŠ΅λ‹ˆλ‹€.

Changes

Cohort / File(s) Change Summary
CI/CD: Jira 이슈 μœ ν˜• μˆ˜μ •
.github/workflows/create-jira-issue.yml
Jira 이슈 생성 λ‹¨κ³„μ˜ issuetype 값을 "Task" β†’ "SubTask"둜 λ³€κ²½

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Pre-merge checks and finishing touches

❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Title Check ⚠️ Warning 제λͺ© β€œchore: QE testing”은 μ‹€μ œ λ³€κ²½ λ‚΄μš©μΈ Jira 이슈 생성 μ›Œν¬ν”Œλ‘œμš°μ˜ 이슈 νƒ€μž…μ„ Taskμ—μ„œ SubTask둜 λ³€κ²½ν•œ 사항을 μ „ν˜€ λ°˜μ˜ν•˜μ§€ μ•Šκ³  QE ν…ŒμŠ€νŠΈμ™€λ„ 관련이 μ—†μ–΄ PR의 핡심을 μš”μ•½ν•˜μ§€ λͺ»ν•©λ‹ˆλ‹€. PR 제λͺ©μ„ β€œchore: Jira 이슈 생성 μ›Œν¬ν”Œλ‘œμš°μ—μ„œ issuetype을 Task μ—μ„œ SubTask 둜 변경” λ“± λ³€κ²½λœ μ„€μ • λ‚΄μš©μ„ λͺ…ν™•νžˆ λ“œλŸ¬λ‚΄λ„λ‘ μˆ˜μ •ν•΄ μ£Όμ‹œκΈ° λ°”λžλ‹ˆλ‹€.
βœ… Passed checks (2 passed)
Check name Status Explanation
Description Check βœ… Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage βœ… Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
πŸ§ͺ Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore-qe

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❀️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions github-actions bot requested a review from clxxrlove October 1, 2025 06:40
@doyeonk429 doyeonk429 changed the title Update create-jira-issue.yml chore: QE testing Oct 1, 2025
@doyeonk429 doyeonk429 merged commit 84fdc17 into develop Oct 1, 2025
3 of 6 checks passed
@doyeonk429 doyeonk429 deleted the chore-qe branch October 1, 2025 06:44
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (3)
.github/workflows/create-jira-issue.yml (3)

106-114: Jira issuetype ν‘œκΈ° 였λ₯˜ κ°€λŠ₯μ„±: SubTask β†’ Sub-task둜 ꡐ체 ν•„μš”

Jira Cloud/Server κΈ°λ³Έ 이슈 νƒ€μž…λͺ…은 보톡 Sub-task μž…λ‹ˆλ‹€. SubTask λŠ” λ§€μΉ­ μ‹€νŒ¨λ‘œ 생성이 400 μ—λŸ¬λ‘œ ν„°μ§ˆ 수 μžˆμŠ΅λ‹ˆλ‹€. ν”„λ‘œμ νŠΈλ³„ μ»€μŠ€ν…€λͺ…이 μ•„λ‹ˆλΌλ©΄ μ•„λž˜μ²˜λŸΌ κ΅μ •ν•˜μ„Έμš”. λ˜ν•œ κ°€λŠ₯ν•˜λ©΄ 이름 λŒ€μ‹  이슈 νƒ€μž… β€œID” μ‚¬μš©μ„ ꢌμž₯ν•©λ‹ˆλ‹€.

-          issuetype: SubTask
+          issuetype: Sub-task

λŒ€μ•ˆ: 이름 λŒ€μ‹  νƒ€μž… IDλ₯Ό μ“°κ±°λ‚˜, with: 블둝에 parent: μž…λ ₯을 직접 μ§€μ •ν•΄ fields μ˜μ‘΄μ„±μ„ 쀄일 수 μžˆμŠ΅λ‹ˆλ‹€.


116-118: 둜그 좜λ ₯ ν‚€ 뢈일치: issueparser_parentKey μ‚¬μš© ν•„μš”

issue-parser 좜λ ₯ ν‚€ 접두사가 λΉ μ Έ ν˜„μž¬λŠ” 빈 값이 찍힐 κ°€λŠ₯성이 ν½λ‹ˆλ‹€.

-        run: echo "Jira Issue ${{ steps.issue-parser.outputs.parentKey }}/${{ steps.create.outputs.issue }} was created"
+        run: echo "Jira Issue ${{ steps.issue-parser.outputs.issueparser_parentKey }}/${{ steps.create.outputs.issue }} was created"

151-157: 이슈 제λͺ© 포맷 μ˜€νƒˆμž: λ‹«λŠ” λŒ€κ΄„ν˜Έ λˆ„λ½

μ˜λ„ν•œ ν˜•μ‹μ΄ [KEY] Title λ₯˜λΌλ©΄ λŒ€κ΄„ν˜Έκ°€ λ‹«νžˆμ§€ μ•Šμ•˜μŠ΅λ‹ˆλ‹€.

-          title: '[${{ steps.create.outputs.issue }}/${{ github.event.issue.title }}'
+          title: '[${{ steps.create.outputs.issue }}] ${{ github.event.issue.title }}'
🧹 Nitpick comments (3)
.github/workflows/create-jira-issue.yml (3)

135-143: 브랜치λͺ… ꡬ성 κ°œμ„ : # μ‚¬μš© μ§€μ–‘ + λ―Έμ‚¬μš© λ³€μˆ˜ slug 처리

# λŠ” Git μžμ²΄λ‘œλŠ” κ°€λŠ₯ν•˜μ§€λ§Œ URL/CLIμ—μ„œ ν˜Όμ„ μ„ μœ λ°œν•©λ‹ˆλ‹€. λ˜ν•œ slug λ₯Ό 계산해 놓고 μ‚¬μš©ν•˜μ§€ μ•ŠμŠ΅λ‹ˆλ‹€. 보닀 μ•ˆμ „ν•œ λ„€μ΄λ°μœΌλ‘œ μ •λ¦¬ν•˜μ„Έμš”.

-          slug=$(echo "$issue_title" | tr '[:upper:]' '[:lower:]' | sed 's/ /-/g' | sed 's/[^a-z0-9\-]//g')
+          slug=$(echo "$issue_title" | tr '[:upper:]' '[:lower:]' | sed 's/ /-/g' | sed 's/[^a-z0-9\-]//g')
           ticket_key="${{ steps.create.outputs.issue }}"
-          branch_name="${ticket_key}-${{ steps.type.outputs.type }}/#${issue_number}"
+          branch_name="${ticket_key}-${{ steps.type.outputs.type }}/${slug:-issue-${issue_number}}"

ν˜Ήμ€ λ‹¨μˆœνžˆ:

-          branch_name="${ticket_key}-${{ steps.type.outputs.type }}/#${issue_number}"
+          branch_name="${ticket_key}-${{ steps.type.outputs.type }}/issue-${issue_number}"

65-69: 쀑볡 체크아웃/브랜치 μ „ν™˜ 정리

Checkout main code (ref: develop) ν›„ λ‹€μ‹œ 체크아웃/νŽ˜μΉ˜ν•˜λŠ” 단계가 μ€‘λ³΅μž…λ‹ˆλ‹€. ν•œ λ‹¨κ³„λ‘œ 합쳐 λŸ¬λ„ˆ μ‹œκ°„ λ‹¨μΆ•ν•˜μ„Έμš”.

  • μ˜΅μ…˜ A: 첫 체크아웃 μ‚­μ œ, 두 번째 체크아웃에 ref: develop + fetch-depth: 0 μ§€μ • ν›„ Switch to develop 단계 제거.
  • μ˜΅μ…˜ B: 첫 μ²΄ν¬μ•„μ›ƒλ§Œ μœ μ§€ν•˜κ³ , 두 번째 체크아웃 및 Switch to develop 제거.

Also applies to: 124-133


101-115: 사전 검증 μΆ”κ°€ ꢌμž₯: parentKey λˆ„λ½ μ‹œ λΉ λ₯Έ μ‹€νŒ¨

μ„œλΈŒνƒœμŠ€ν¬λŠ” λΆ€λͺ¨ ν‚€κ°€ ν•„μˆ˜μž…λ‹ˆλ‹€. νŒŒμ„œκ°€ 값을 λͺ» κ°€μ Έμ˜€λ©΄ 생성 λ‹¨κ³„μ—μ„œ 400이 λ‚©λ‹ˆλ‹€. 생성 μ „ κ°„λ‹¨ν•œ κ°€λ“œ μΆ”κ°€λ₯Ό ꢌμž₯ν•©λ‹ˆλ‹€.

       - name: Create Issue
         id: create
         uses: atlassian/gajira-create@v3
+        if: ${{ steps.issue-parser.outputs.issueparser_parentKey != '' }}
         with:
           project: BOOK
           issuetype: Sub-task
           summary: '${{ github.event.issue.title }}'
           description: '${{ steps.md2jira.outputs.output-text }}'
           fields: |
             {
               "parent": {
                 "key": "${{ steps.issue-parser.outputs.issueparser_parentKey }}"
               }
             }

λ˜λŠ” λ°”λ‘œ μ•žμ— μ…Έ κ°€λ“œλ₯Ό μΆ”κ°€:

- name: Validate parent key
  run: |
    if [ -z "${{ steps.issue-parser.outputs.issueparser_parentKey }}" ]; then
      echo "::error::Missing parent issue key (issueparser_parentKey)."
      exit 1
    fi
πŸ“œ Review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

πŸ“₯ Commits

Reviewing files that changed from the base of the PR and between a379665 and 2431e30.

πŸ“’ Files selected for processing (1)
  • .github/workflows/create-jira-issue.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: build

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants