Chore/CI

[leeunduck]

🚀 Pull Request

📝 PR 유형

• 기능 추가 (Feature)
• 버그 수정 (Bug Fix)
• 코드 개선 (Refactoring)
• 문서 작업 (Docs)
• 환경 설정 (Configuration)
• 최종 점검 (Release Check)

---

🔍 변경 사항

기능 브랜치에서 push와 develop에서 main으로 PR을 생성했을시에만 CI를 하도록 바꿈
기능 브랜치에서 develop으로 PR을 열었을 때 CI는 제거함

---

📸 스크린샷

---

🚧 관련 이슈

---

🛠️ 최종 배포 점검 리스트

• 주요 기능 동작 확인
• 빌드/배포 환경 점검
• 문서/설정 검토

---

✅ 최종 배포 점검 결과

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
custom-daily-planner	Ready	Preview	Comment	Sep 22, 2025 6:30pm

[chatgpt-codex-connector]

Codex Review: Here are some suggestions.

Reply with @codex fix comments to fix any unresolved comments.

About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you open a pull request for review, mark a draft as ready, or comment "@codex review". If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex fix this CI failure" or "@codex address that feedback".

[chatgpt-codex-connector]

[P1] CI never runs when PR retargeted to main

Restricting pull_request.types to opened, reopened, synchronize, and ready_for_review unintentionally drops the edited event. If a feature PR is initially opened against develop (so CI doesn’t run) and later retargeted to main, GitHub only emits an edited event, so this workflow never fires and the code can merge into main without any CI checks. Add edited (or remove the types filter) so retargeting a PR to main still triggers the pipeline.

Useful? React with 👍 / 👎.