Skip to content

Commit

Permalink
fix: set token param correctly (#361)
Browse files Browse the repository at this point in the history
* fix: set token param correctly

* fix: more cappp bump configurations

* chore: add tag to automated cappp pr
  • Loading branch information
faiq authored May 31, 2022
1 parent fdd24db commit 70d7200
Showing 1 changed file with 10 additions and 6 deletions.
16 changes: 10 additions & 6 deletions .github/workflows/release-main.yml
Original file line number Diff line number Diff line change
Expand Up @@ -51,10 +51,9 @@ jobs:
DOCKER_CLI_EXPERIMENTAL: "enabled"
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
WHAT: make release

bump-kib:
runs-on: ubuntu-latest
needs: release-please
runs-on: ubuntu-latest
steps:
- if: ${{ needs.release-please.outputs.release_created }}
name: Setup Go
Expand All @@ -67,23 +66,28 @@ jobs:
uses: actions/checkout@v3
with:
repository: mesosphere/cluster-api-provider-preprovisioned
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
submodules: true
token: ${{ secrets.GITHUB_TOKEN }}
path: cluster-api-provider-preprovisioned
fetch-depth: 0

- if: ${{ needs.release-please.outputs.release_created }}
run: git config --global --add safe.directory "$GITHUB_WORKSPACE"

- if: ${{ needs.release-please.outputs.release_created }}
name: Update KIB in CAPPP
run: make update-kib
working-directory: cluster-api-provider-preprovisioned
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

- if: ${{ needs.release-please.outputs.release_created }}
name: Create Pull Request for KIB bump in CAPPP
uses: peter-evans/create-pull-request@v4
working-directory: cluster-api-provider-preprovisioned
with:
token: ${{ secrets.MESOSPHERECI_USER_TOKEN }}
add-paths: preprovsioned/kib
add-paths: preprovisioned/kib
body: bumps KIB to latest version
commit: "feat: bump kib to latest"
commit: "feat: bump kib to ${{ needs.release-please.outputs.release_tag_name }}"
path: cluster-api-provider-preprovisioned
title: "feat: bump kib to ${{ needs.release-please.outputs.release_tag_name }}"

0 comments on commit 70d7200

Please sign in to comment.