Skip to content

Commit

Permalink
syntax error
Browse files Browse the repository at this point in the history
  • Loading branch information
whitfiea committed Apr 24, 2024
1 parent 6648659 commit 4299577
Showing 1 changed file with 24 additions and 25 deletions.
49 changes: 24 additions & 25 deletions .github/workflows/update-internal-repo.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -8,32 +8,31 @@ on:
jobs:
update-repo:
runs-on: ubuntu-latest
steps:
- name: Checkout local repo
uses: actions/checkout@v4
with:
path: source
steps:
- name: Checkout local repo
uses: actions/checkout@v4
with:
path: source

- name: Checkout remote repo
uses: actions/checkout@v4
with:
github-server-url: https://github.ibm.com
repository: automation-paas-cd-pipeline/mas-gitops
ref: ${GITHUB_REF##*/}
token: ${{ secrets.ACTIONS_GITHUB_TOKEN }}
path: target
- name: Checkout remote repo
uses: actions/checkout@v4
with:
github-server-url: https://github.ibm.com
repository: automation-paas-cd-pipeline/mas-gitops
ref: ${GITHUB_REF##*/}
token: ${{ secrets.ACTIONS_GITHUB_TOKEN }}
path: target

- name: Copy over files
run: $GITHUB_WORKSPACE/build/bin/copy-gitops.sh -s $GITHUB_WORKSPACE/source -t $GITHUB_WORKSPACE/target
- name: Copy over files
run: $GITHUB_WORKSPACE/build/bin/copy-gitops.sh -s $GITHUB_WORKSPACE/source -t $GITHUB_WORKSPACE/target

- name: Setup git config
run: |
cd $GITHUB_WORKSPACE/target
git config user.name "GitHub Actions Bot"
git config user.email "<>"
- name: Setup git config
run: |
cd $GITHUB_WORKSPACE/target
git config user.name "GitHub Actions Bot"
git config user.email "<>"
- name: Commit changes to remote repo
run: |
echo "Push changes to ${GITHUB_REF##*/} branch of https://github.ibm.com/automation-paas-cd-pipeline/mas-gitops"
git push origin ${GITHUB_REF##*/}
- name: Commit changes to remote repo
run: |
echo "Push changes to ${GITHUB_REF##*/} branch of https://github.ibm.com/automation-paas-cd-pipeline/mas-gitops"
git push origin ${GITHUB_REF##*/}

0 comments on commit 4299577

Please sign in to comment.