Update Cargo.lock #44
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
| name: "Update Cargo.lock" | |
| on: | |
| schedule: | |
| - cron: '0 3 * * 1' # On Monday, 03:00 UTC | |
| workflow_dispatch: {} | |
| jobs: | |
| cargo_update: | |
| runs-on: ubuntu-latest | |
| steps: | |
| - uses: actions/checkout@v4 # Only implemented for `main` branch. | |
| - uses: actions-rust-lang/[email protected] | |
| - run: echo "BRANCH_NAME=automation/cargo_update$(date +%s)" >> "$GITHUB_OUTPUT" | |
| id: branch_name | |
| - run: git checkout -b ${{ steps.branch_name.outputs.BRANCH_NAME }} | |
| - run: cargo update | |
| # We should create an automation user here. | |
| - run: git config --global user.email "[email protected]" | |
| - run: git config --global user.name "Solomon Jacobs" | |
| - run: git add . | |
| # This git commit may be empty, in which case this step will fail. However, since this action | |
| # runs only once a week, this should not affect us. Any error is likely worth investigating. | |
| - run: git commit -m "Update Cargo.lock" -m "Created automatically." -o Cargo.lock | |
| - run: git push origin HEAD | |
| - name: "Create pull request" | |
| # This command does not trigger any workflow. We can fix this by creating an automation | |
| # user with a Personal Access Token. See discussion here: | |
| # https://github.com/peter-evans/create-pull-request/issues/48 | |
| run: gh pr create -B main -H ${{ steps.branch_name.outputs.BRANCH_NAME }} -f | |
| env: | |
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} |