Skip to content

workflow에서의 jira issue 연결 방식 수정#21

Merged
yoouyeon merged 6 commits intodevelopfrom
chore/MD-10
Feb 17, 2026
Merged

workflow에서의 jira issue 연결 방식 수정#21
yoouyeon merged 6 commits intodevelopfrom
chore/MD-10

Conversation

@yoouyeon
Copy link
Contributor

@yoouyeon yoouyeon commented Feb 17, 2026

💻 작업 내용

  • 새로 만들어진 워크스페이스에 맞게 jira key 변경했습니다.
  • issue 링크를 본문에 추가하는 대신 comment로 추가하도록 수정했습니다.

Summary by CodeRabbit

  • Chores
    • 내부 GitHub Actions 워크플로우 업데이트:
      • PR 작성자 자동 할당 작업 비활성화
      • PR에서 감지된 JIRA 키를 기반으로 PR 본문 대신 PR 코멘트에 간결한 JIRA 링크 게시
      • 리포지토리 체크아웃 단계 추가 및 처리 로직 간소화(추가 도구 설치·본문 업데이트 제거)
      • JIRA 키가 있을 때만 링크 게시되도록 조건화 및 키 패턴 변경 반영

- 새로 만들어진 워크스페이스에 맞게 jira key 변경
- issue 링크를 본문에 추가하는 대신 comment로 추가하도록 수정
@yoouyeon yoouyeon self-assigned this Feb 17, 2026
@yoouyeon yoouyeon added the 🧹 Chore 설정·잡무 작업 label Feb 17, 2026
@github-actions github-actions bot requested a review from ongheong February 17, 2026 13:09
@coderabbitai
Copy link

coderabbitai bot commented Feb 17, 2026

📝 Walkthrough

Walkthrough

PR 검토 워크플로우에서 PR 작성자 지정(assign) 작업이 주석 처리되어 비활성화되었고, JIRA 키 추출이 HEAD_REF 환경 변수에서 이루어지도록 변경(정규식 MD-[0-9]+)되었습니다. PR 본문 직접 수정(REST API)은 제거되고 JIRA 링크를 PR 댓글로 추가하는 방식으로 대체되었습니다.

Changes

Cohort / File(s) Summary
Workflow file
​.github/workflows/pr-review-manager.yml
assign 작업이 전체 주석 처리되어 더 이상 실행되지 않음. add-jira-link 작업의 조건 라인이 주석 처리되어 permissions가 무조건 정의됨; checkout 단계 추가.
JIRA key extraction
​.github/workflows/pr-review-manager.yml
JIRA 키 추출이 github.head_ref 기반의 HEAD_REF 환경 변수로 이동하고 정규식이 MD-[0-9]+로 변경됨. 추출 결과는 jira_key 출력으로 유지됨.
PR update mechanism
​.github/workflows/pr-review-manager.yml
기존에 사용되던 jq 설치 및 REST API를 통한 PR 본문 업데이트 로직 제거. 대신 thollander/actions-comment-pull-request@v3 액션으로 JIRA 링크를 마크다운 형식의 PR 댓글로 게시하도록 변경(조건: jira_key 존재 시).
Control flow & cleanup
​.github/workflows/pr-review-manager.yml
PR 본문 수정 대신 댓글 작성 흐름으로 전환; PR 본문 업데이트 관련 단계들이 삭제되어 실행 경로 단순화됨.

Poem

🐰 깡충, 코드숲을 훑어보니,
HEAD_REF에 숨은 키를 찾았네, MD-숫자 춤추고,
본문은 건드리지 않고 댓글로 살짝,
링크 하나 달랑, 깔끔하게 완료! ✨

🚥 Pre-merge checks | ✅ 1
✅ Passed checks (1 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch chore/MD-10

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.

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: 1

Caution

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

⚠️ Outside diff range comments (1)
.github/workflows/pr-review-manager.yml (1)

23-25: ⚠️ Potential issue | 🟠 Major

add-jira-link job에 permissions 설정이 누락되었습니다.

assign job에는 permissions: pull-requests: write가 명시되어 있지만, add-jira-link job에는 없습니다. thollander/actions-comment-pull-request 액션이 PR에 코멘트를 작성하려면 pull-requests: write 권한이 필요합니다. 리포지토리 기본 권한 설정에 따라 동작할 수도 있지만, 명시적으로 선언하는 것이 안전합니다.

🔧 수정 제안
   add-jira-link:
     runs-on: ubuntu-latest
+    permissions:
+      pull-requests: write
     if: github.event.action == 'opened'
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/pr-review-manager.yml around lines 23 - 25, The
add-jira-link job is missing an explicit permissions block required for
thollander/actions-comment-pull-request to post comments; add a permissions:
pull-requests: write entry under the add-jira-link job (same style as the assign
job) so the job has explicit pull-requests write scope before the
thollander/actions-comment-pull-request step runs.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/pr-review-manager.yml:
- Around line 31-33: 타겟 스크립트에서 echo 명령 앞에 불필요한 공백이 들어가 있어 들여쓰기가 맞지 않으니, JIRA_KEY
변수를 출력하는 echo 호출(현재 `echo "jira_key=$JIRA_KEY" >> "$GITHUB_OUTPUT"`)의 앞 공백을 제거해
`JIRA_KEY=$(...)` 라인과 동일한 들여쓰기 수준으로 정렬하세요.

---

Outside diff comments:
In @.github/workflows/pr-review-manager.yml:
- Around line 23-25: The add-jira-link job is missing an explicit permissions
block required for thollander/actions-comment-pull-request to post comments; add
a permissions: pull-requests: write entry under the add-jira-link job (same
style as the assign job) so the job has explicit pull-requests write scope
before the thollander/actions-comment-pull-request step runs.

@yoouyeon yoouyeon marked this pull request as draft February 17, 2026 13:31
@yoouyeon yoouyeon marked this pull request as ready for review February 17, 2026 13:31
@github-actions
Copy link

github-actions bot commented Feb 17, 2026

📝 관련 이슈

MD-10

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: 1

🧹 Nitpick comments (1)
.github/workflows/pr-review-manager.yml (1)

29-32: Checkout step은 이 job에서 불필요합니다.

이 job은 github.head_ref 환경 변수에서 브랜치 이름을 추출하고 PR 댓글만 작성하므로 소스 코드 checkout이 필요하지 않습니다. 제거하면 워크플로우 실행 시간을 약간 단축할 수 있습니다.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/pr-review-manager.yml around lines 29 - 32, Remove the
unnecessary checkout step named "Checkout source code" that uses
actions/checkout@v4: since this job only reads github.head_ref and posts a PR
comment, it doesn't require the repository to be checked out; delete the entire
step block that contains "name: Checkout source code" and "uses:
actions/checkout@v4" (and its with: fetch-depth) to shorten runtime.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Inline comments:
In @.github/workflows/pr-review-manager.yml:
- Around line 25-27: The workflow currently has the conditional "if:
github.event.action == 'opened'" commented out causing the job to run on both
opened and ready_for_review events and potentially post duplicate JIRA-link
comments; either restore that if condition to run only on 'opened' or
(preferred) configure the thollander/actions-comment-pull-request@v3 step to use
the comment_tag option so the action updates an existing comment instead of
creating a new one (look for the job that invokes
thollander/actions-comment-pull-request@v3 and add comment_tag with a stable tag
string, or re-enable the if: github.event.action == 'opened' guard).

---

Nitpick comments:
In @.github/workflows/pr-review-manager.yml:
- Around line 29-32: Remove the unnecessary checkout step named "Checkout source
code" that uses actions/checkout@v4: since this job only reads github.head_ref
and posts a PR comment, it doesn't require the repository to be checked out;
delete the entire step block that contains "name: Checkout source code" and
"uses: actions/checkout@v4" (and its with: fetch-depth) to shorten runtime.

@yoouyeon
Copy link
Contributor Author

@coderabbitai approve

@coderabbitai
Copy link

coderabbitai bot commented Feb 17, 2026

✅ Actions performed

Comments resolved and changes approved.

1 similar comment
@coderabbitai
Copy link

coderabbitai bot commented Feb 17, 2026

✅ Actions performed

Comments resolved and changes approved.

@yoouyeon
Copy link
Contributor Author

후속 작업을 위해서 이 PR은 머지하겠습니다!!!!

@yoouyeon yoouyeon merged commit c410121 into develop Feb 17, 2026
1 check passed
@yoouyeon yoouyeon deleted the chore/MD-10 branch February 17, 2026 13:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

🧹 Chore 설정·잡무 작업

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant