Conversation
[FEAT] 로그인 구현
[FEAT] 부품 조회 화면 구현
SPM-175 주문관리 구현 / 주문 로직 구현
[FEAT] 대시보드 UI 구성
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
[SPM-329] 주문 로직 수정, 예외 처리 전역 스낵바 적용, 패키지 구조 리팩토링
[FIX] 로그인, 회원가입 로직 수정 / 설정 화면 구성
[REFAC] 직급 Enum 변경
[FEAT] 부품 가격 추가
[FEAT] 대시보드 api 연동
| uses: 33-Auto/.github/.github/workflows/reusable-pr-reminder.yml@main | ||
| secrets: | ||
| # 해당 시크릿은 조직의 시크릿에 저장되어 있음 | ||
| SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }} | ||
| with: | ||
| SLACK_USER_MAP: ${{ vars.SLACK_USER_MAP }} No newline at end of file |
Check warning
Code scanning / CodeQL
Workflow does not contain permissions Medium
Show autofix suggestion
Hide autofix suggestion
Copilot Autofix
AI 3 months ago
To fix this issue, add an explicit permissions block at the root of the workflow file (above on:), as all jobs in the workflow that do not have their own permissions key will inherit these settings. The best approach is to start with minimal permissions and increment as necessary. Since the job is used to send Slack notifications related to PRs and uses secrets, it's best to set contents: read and pull-requests: read as a minimal safe configuration, unless further write permissions are required for PRs (e.g., editing, commenting). Update lines at the top of .github/workflows/pr-reminder.yml to add:
permissions:
contents: read
pull-requests: readIf in the future you require more permissions (such as issues: write or pull-requests: write), you can further increase granularity.
| @@ -1,4 +1,7 @@ | ||
| name: PR Reminder | ||
| permissions: | ||
| contents: read | ||
| pull-requests: read | ||
|
|
||
| on: | ||
| schedule: |
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing touches🧪 Generate unit tests (beta)
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. Comment |
No description provided.