turbolift
turbolift copied to clipboard
A simple tool to help apply changes across many GitHub repositories simultaneously
Bumps [golangci/golangci-lint-action](https://github.com/golangci/golangci-lint-action) from 4.0.0 to 5.1.0. Release notes Sourced from golangci/golangci-lint-action's releases. v5.1.0 What's Changed Changes feat: support for pull and merge_group events with the option only-new-issues by @ldez in...
Using a PR to kick off a conversation about conventional commit styles and whether we should use it for turbolift. I've been using it and seen it used here and...
Adding the Build status to the pr-status list command using the `StatusCheckRollup` field from the github pr status command. `StatusCheckRollup` contains a list with all the checks for the PR...
I came to this repo from this [blog post](https://www.jvt.me/posts/2023/01/21/bulk-git-repo-changes/) because I was curious if GitLab support is something that is planned or at least considered. I couldn't find an issue...
To deal with https://github.com/Skyscanner/turbolift/issues/124 Also adds a missing test for creating PRs with custom description file. Currently failing because changes to the PR body aren't detected - need to look...
A suggestion from my teammate @lnascimentosilva shortly after using turbolift for the first time: It would make sense to block the `create-prs` or at least ask for confirmation if the...
We are pulling from upstream after cloning a fork to make sure we have the latest commits (see https://github.com/Skyscanner/turbolift/issues/80), but this doesn't work if there is a conflict, i.e. the...
On large repo lists, one often has to run this kind of workflow: ```console turbolift clone turbolift forearch ``` then, to _validate_ the changes, they would run something like this:...
at the moment all prs commits etc are sequential. For large numbers, adding parallel processing could improve the user experience by accelerating the feedback loop.
Reverts Skyscanner/turbolift#116 We are re-implementing the depth=1 feature with the addition of --no-single-branch to prevent issues as described in #104