Skip to content

chore: CI 트리거 브랜치 패턴 확장#331

Open
2Jin1031 wants to merge 4 commits into
mainfrom
chore/ci-branch-pattern
Open

chore: CI 트리거 브랜치 패턴 확장#331
2Jin1031 wants to merge 4 commits into
mainfrom
chore/ci-branch-pattern

Conversation

@2Jin1031

Copy link
Copy Markdown
Contributor

Summary

  • pull_request.yml의 branches를 ["main"]에서 ["main", "feat/**", "fix/**", "refactor/**"]로 확장
  • feature branch를 base로 하는 자식 PR에서도 CI가 동작하도록 변경

Test plan

  • feature branch 대상 PR 생성 시 CI 트리거 확인

Closes #330

Generated with Claude Code

feature branch 대상 자식 PR에서도 CI가 동작하도록
branches 패턴에 feat/**, fix/**, refactor/** 추가

Closes #330

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: af94bc04fc

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment thread build.gradle Outdated
dependencies {
implementation 'org.springframework.boot:spring-boot-starter-data-jpa'
implementation 'org.springframework.boot:spring-boot-starter-web'
implementation 'org.springframework.boot:spring-boot-starter-security'

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Remove unintended Spring Security starter

Adding spring-boot-starter-security here enables Spring Boot's default web security for the whole application; I checked the repo for SecurityFilterChain, @EnableWebSecurity, authorizeHttpRequests, and permitAll and found no security configuration to reopen the existing public /api/** controllers. In a deployed app this will turn unauthenticated requests into 401/login challenges, including endpoints like /api/subjects, /api/notices, and /api/connect, which is unrelated to the CI trigger change and would break clients unless a matching security config is added.

Useful? React with 👍 / 👎.

@chemistryx chemistryx force-pushed the chore/ci-branch-pattern branch 2 times, most recently from 3d99176 to 80d9906 Compare June 20, 2026 07:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

chore: CI 트리거 브랜치 패턴 확장

1 participant