You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As raised in arup-group/genet#234 it's probably nicer to have the cruft template check and update done in a separate workflow and automatically raised as a new PR.
There's a dependency manager that might be updated with a bot to solve this issue for us: renovatebot/renovate#24000
In the meantime, we could run this as its own workflow job (see below). I tried this in a boilerplate repo that I have but it comes with the issue that sometimes cruft needs to update the CI workflows themselves. This requires extra-special write permissions that can can only come from a personal access token. I'm not comfortable with setting up this level of write permissions for a CI action that would be deployed across all template-derived repos. So, for now, I think we wait to see if a bot comes about
jobs:
cruftupdate:
runs-on: ubuntu-latestpermissions:
contents: writesteps:
- name: Checkout the repouses: actions/checkout@v4
- name: Set up dependenciesuses: mamba-org/setup-micromamba@v1with:
micromamba-version: latestenvironment-name: ${{ github.event.repository.name }}-cruftcreate-args: cruft python=3.11post-cleanup: allcache-environment: true
- name: Add dummy GitHub credentialsrun: | git config --global user.name Cruft check git config --global user.email [email protected]
- name: Check project against templateid: checkrun: cruft checkcontinue-on-error: true
- name: Check on failuresif: steps.check.outcome != 'success'run: cruft update -y
- name: Create Pull Requestuses: peter-evans/create-pull-request@v6with:
commit-message: Cruft - update against templatetitle: Cruft - update against templatebody: | # Cruft - update against template Before you merge this PR, ensure all merge conflicts (documented in `.rej` files have been resolved)base: mainlabels: automated-pr, templatebranch: cruft-updatedelete-branch: true
Version
v0.2.0
The text was updated successfully, but these errors were encountered:
What can be improved?
As raised in arup-group/genet#234 it's probably nicer to have the cruft template check and update done in a separate workflow and automatically raised as a new PR.
There's a dependency manager that might be updated with a bot to solve this issue for us: renovatebot/renovate#24000
In the meantime, we could run this as its own workflow job (see below). I tried this in a boilerplate repo that I have but it comes with the issue that sometimes cruft needs to update the CI workflows themselves. This requires extra-special write permissions that can can only come from a personal access token. I'm not comfortable with setting up this level of write permissions for a CI action that would be deployed across all template-derived repos. So, for now, I think we wait to see if a bot comes about
Version
v0.2.0
The text was updated successfully, but these errors were encountered: