Skip to content

Commit

Permalink
Merge pull request #11 from Swaggy-Swagger/leejin-rho-patch-1
Browse files Browse the repository at this point in the history
fix: 불필요하게 에러 일으키는 workflow 코드 삭제
  • Loading branch information
leejin-rho authored Oct 29, 2024
2 parents 894b864 + 0db28d4 commit ec86eb4
Showing 1 changed file with 2 additions and 27 deletions.
29 changes: 2 additions & 27 deletions .github/workflows/sync-to-backend-repo.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ on:
branches:
- master
types:
- closed # PR이 master에 머지될 때만
- closed # PR이 master에 병합될 때만

jobs:
sync_files:
Expand All @@ -20,32 +20,6 @@ jobs:
npm install # 또는 yarn install
npm run build # 또는 yarn build
# Configure Git with PR Author
- name: Configure Git with PR Author
run: |
if [[ "${{ github.event.pull_request.merged }}" == 'true' ]]; then
git config --global user.name "${{ github.event.pull_request.user.login }}"
git config --global user.email "${{ github.event.pull_request.user.login }}@users.noreply.github.com"
fi
# Commit with PR Author info
- name: Amend Commit with Author Info
run: |
if [[ "${{ github.event.pull_request.merged }}" == 'true' ]]; then
git commit --amend --no-edit --author="${{ github.event.pull_request.user.login }} <${{ github.event.pull_request.user.login }}@users.noreply.github.com>"
git push origin main --force
echo "Git user.name: $(git config user.name)"
fi
# Commit with PR Title as Message
- name: Commit with PR Title as Message
run: |
if [[ "${{ github.event.pull_request.merged }}" == 'true' ]]; then
git commit --amend --no-edit --author="${{ github.event.pull_request.user.login }} <${{ github.event.pull_request.user.login }}@users.noreply.github.com>"
git commit -m "${{ github.event.pull_request.title }}"
git push origin main --force
fi
- name: Sync Files to Backend Repository
run: |
if [[ "${{ github.event.pull_request.merged }}" == 'true' ]]; then
Expand Down Expand Up @@ -77,3 +51,4 @@ jobs:
env:
GITHUB_TOKEN: ${{ secrets.PAT }}

0 comments on commit ec86eb4

Please sign in to comment.