Skip to content

Chore(project): 이슈 및 PR 작성 시 Assignees 자동 할당#298

Merged
jin-evergreen merged 1 commit intodevelopfrom
chore/assignees/#297
Mar 4, 2026
Merged

Chore(project): 이슈 및 PR 작성 시 Assignees 자동 할당#298
jin-evergreen merged 1 commit intodevelopfrom
chore/assignees/#297

Conversation

@jin-evergreen
Copy link
Copy Markdown
Member

📌 Summary

이슈 및 PR 작성 시 라벨 뿐 아니라 Assignees도 자동 할당되도록 했습니다.

📚 Tasks

  • assign-auto-label.yml 파일 수정

🔍 Describe

이슈 및 PR 작성 시 Assignees 자동 할당

기존에는 라벨만 자동 할당되도록 설정했는데, Assignees도 함께 자동으로 할당되도록 관련 로직을 추가했습니다.

👀 To Reviewer

  • 개선 사항이 있다면 알려주세요!

@jin-evergreen jin-evergreen self-assigned this Mar 4, 2026
@jin-evergreen jin-evergreen requested a review from a team as a code owner March 4, 2026 16:40
@jin-evergreen jin-evergreen linked an issue Mar 4, 2026 that may be closed by this pull request
@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 4, 2026

📝 Walkthrough

Summary by CodeRabbit

새로운 기능

  • 이슈 및 풀 요청이 개설될 때 자동으로 작성자에게 할당되는 기능을 추가했습니다. 기존 레이블 할당 기능과 함께 작동합니다.

Walkthrough

이슈/PR이 생성될 때 레이블 추가와 함께 작성자에게 자동으로 할당하는 기능을 추가했어요. 기존 레이블 처리 플로우 이후에 assign 로직이 실행되며, 에러 발생 시에도 워크플로우 실패는 방지하는 구조입니다.

Changes

Cohort / File(s) Summary
GitHub Actions 워크플로우
.github/workflows/assign-auto-label.yml
이슈 자동 할당 기능 추가: github.rest.issues.addAssignees 호출을 통해 issue/PR 작성자 자동 할당 처리 추가, 레이블 추가 이후 실행되며 에러 발생 시 워크플로우 계속 진행

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Suggested labels

🐻‍❄️ 진석, 🔧 Chore

Suggested reviewers

  • Sohyunnnn
  • eunkr82
🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Title check ✅ Passed PR 제목은 [type] 형식을 따르고 44자로 50자 이내 요구사항을 충족하며, 이슈와 PR 작성 시 자동 할당 기능 추가라는 변경사항을 명확히 설명합니다.
Description check ✅ Passed PR 설명은 #297 링크, Assignees 자동 할당 기능 추가의 목적, 수정 파일, 그리고 구현 내용을 명확히 기술하고 있습니다.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

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


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 added 🐻‍❄️ 진석 🔧 Chore 빌드, 패키지 설정 등 기타 작업 labels Mar 4, 2026
Copy link
Copy Markdown

@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

🤖 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/assign-auto-label.yml:
- Around line 78-86: The empty catch swallowing errors around the
github.rest.issues.addAssignees call hides failures; update the catch block that
wraps github.rest.issues.addAssignees (the try/catch surrounding issueNumber and
assignees: [author]) to log a warning including the caught error and context
(e.g., issueNumber and author) instead of doing nothing—use the Action logger
(core.warning or console.warn) to emit a clear message like "Failed to add
assignee" plus the error details so failures remain non-fatal but are
discoverable.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 132eec50-ff4b-42fc-ad7e-413fe47c861c

📥 Commits

Reviewing files that changed from the base of the PR and between e63bcf4 and 096e6a4.

📒 Files selected for processing (1)
  • .github/workflows/assign-auto-label.yml

Comment on lines +78 to +86
try {
await github.rest.issues.addAssignees({
owner: context.repo.owner,
repo: context.repo.repo,
issue_number: issueNumber,
assignees: [author]
});
} catch (error) {
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

Must: 자동 할당 실패를 조용히 무시하지 않도록 로그를 남겨 주세요.

Line 85-86에서 예외를 비워두면 할당 실패 시 원인 추적이 어려워집니다. 워크플로우를 실패시키지 않는 현재 방향은 유지하되, 최소한 경고 로그는 남겨 주시는 것이 좋습니다.

제안 패치
             try {
               await github.rest.issues.addAssignees({
                 owner: context.repo.owner,
                 repo: context.repo.repo,
                 issue_number: issueNumber,
                 assignees: [author] 
               });
             } catch (error) {
+              console.warn(
+                `[auto-labeler] failed to assign "${author}" to #${issueNumber}: ${error?.message || error}`
+              );
             }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
try {
await github.rest.issues.addAssignees({
owner: context.repo.owner,
repo: context.repo.repo,
issue_number: issueNumber,
assignees: [author]
});
} catch (error) {
}
try {
await github.rest.issues.addAssignees({
owner: context.repo.owner,
repo: context.repo.repo,
issue_number: issueNumber,
assignees: [author]
});
} catch (error) {
console.warn(
`[auto-labeler] failed to assign "${author}" to #${issueNumber}: ${error?.message || error}`
);
}
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/assign-auto-label.yml around lines 78 - 86, The empty
catch swallowing errors around the github.rest.issues.addAssignees call hides
failures; update the catch block that wraps github.rest.issues.addAssignees (the
try/catch surrounding issueNumber and assignees: [author]) to log a warning
including the caught error and context (e.g., issueNumber and author) instead of
doing nothing—use the Action logger (core.warning or console.warn) to emit a
clear message like "Failed to add assignee" plus the error details so failures
remain non-fatal but are discoverable.

Copy link
Copy Markdown
Contributor

@Sohyunnnn Sohyunnnn left a comment

Choose a reason for hiding this comment

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

👍👍👍 진석님 덕분에 DX가 한층 편해지는 거 같아요 감사합니다 !!

Copy link
Copy Markdown
Contributor

@eunkr82 eunkr82 left a comment

Choose a reason for hiding this comment

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

Image

@jin-evergreen jin-evergreen merged commit 00dd363 into develop Mar 4, 2026
3 checks passed
@jin-evergreen jin-evergreen deleted the chore/assignees/#297 branch March 15, 2026 05:25
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.

[Chore] 이슈 및 PR 작성 시 Assignees 자동 할당

3 participants