ci: Correct branch name in release please workflow #1
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| on: | |
| push: | |
| branches: | |
| - master | |
| permissions: | |
| contents: write | |
| pull-requests: write | |
| name: release-please | |
| jobs: | |
| release-please: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - uses: google-github-actions/release-please-action@v4 | |
| with: | |
| # this assumes that you have created a personal access token | |
| # (PAT) and configured it as a GitHub action secret named | |
| # `MY_RELEASE_PLEASE_TOKEN` (this secret name is not important). | |
| token: ${{ secrets.RELEASE_PLEASE_TOKEN }} | |
| # this is a built-in strategy in release-please, see "Action Inputs" | |
| # for more options | |
| release-type: rust |