Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: #1 포크의 경우 main브랜치 이름 추가 #9

Merged
merged 3 commits into from
Jul 3, 2024

Conversation

leeminhee119
Copy link
Member

main 브랜치명 추가


🏄🏼‍♂️‍ Summary (요약)

  • main 브랜치명 추가

🫨 Describe your Change (변경사항)

  • 포크해서 PR하는 경우 워크플로가 작동을 안하더라구요!
  • 포크하고 PR하는 경우 브랜치명 앞에 organization/repo 가 붙는데 이 부분 때문인 것 같아요. 추가해줬습니다!

🧐 Issue number and link (참고)

📚 Reference (참조)

@leeminhee119 leeminhee119 self-assigned this Jul 2, 2024
@leeminhee119 leeminhee119 added the ✌🏻 bugfix It's work! label Jul 2, 2024
@leeminhee119
Copy link
Member Author

.. 라고 생각했는데, 왜 그래도 안될까요 🤨

@@ -4,7 +4,7 @@ import { useAtom } from "jotai";
import { messageAtom } from "@/store/messageAtom.tsx";

function MainPage() {
const [message, setMessage] = useAtom(messageAtom);
const [message] = useAtom(messageAtom);
Copy link
Member

@klmhyeonwoo klmhyeonwoo Jul 2, 2024

Choose a reason for hiding this comment

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

변수를 없애는 것도 방법인데, 추후에 사용하는거면 임시로 이런 방법도 있어요!

Suggested change
const [message] = useAtom(messageAtom);
const [message, _] = useAtom(messageAtom);

지금 이 부분 때문에 빌드 실패나는데 잡아주셔서 감사합니다 😊

@klmhyeonwoo
Copy link
Member

.. 라고 생각했는데, 왜 그래도 안될까요 🤨

어랏 저거 추가해도 안되나요.. 🤔

@@ -4,9 +4,11 @@ on:
push:
branches:
- main
- depromeet/layer:main
pull_request:
Copy link
Member

@klmhyeonwoo klmhyeonwoo Jul 2, 2024

Choose a reason for hiding this comment

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

이렇게 하면 되려나요?! 🫨
찾은 레퍼런스 자료 공유드립니다!

정리하면 pull_request 이벤트가 PR로 올라온 커밋에서 실행되는 반면 pull_request_target은 풀 리퀘스트에 의해서 실행되는 이벤트이지만 풀 리퀘스트가 머지 대상(target)으로 지정한 base를 기준으로 실행된다.

Suggested change
pull_request:
pull_request_target:

참조 : https://blog.outsider.ne.kr/1541


Copy link
Member Author

Choose a reason for hiding this comment

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

와 빠르다 !! 적용해볼게요

Copy link
Member

Choose a reason for hiding this comment

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

🚀

Copy link
Member Author

@leeminhee119 leeminhee119 Jul 2, 2024

Choose a reason for hiding this comment

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

흠,, 보니까 애초에 포크한 PR은 신뢰할 수 없다고 판단해서 이 이벤트로도 빌드는 하지 말라고 하는 것 같네요..?! (Warning 참고)

-> 7/3 확인: 포크 PR 워크플로 작동!

@leeminhee119 leeminhee119 merged commit 00f1445 into main Jul 3, 2024
@leeminhee119 leeminhee119 deleted the feature/1/build-workflow branch July 4, 2024 04:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
✌🏻 bugfix It's work!
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants