Sebastien Le Digabel
Sebastien Le Digabel
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.
We have lots of unit tests, but we can't assert whether turbolift does what it's supposed to do. We would want to have minimal CI integration testing with the following:...
As part of #75 I saw some limitations in the logging because the logger is instantiated in the command itself. That limits for instance the use of logs within functions...
As a user when I run turbolift I would want to predefined settings to be used from a config file instead of typing it all
This came up during the Turbolift post mortem, having the ability to file a PR on small % of the repositories first before expanding this to all repositories.
The current `turbolift` command would create a PR based on a fork by default unless passed the `--no-fork` flag. It would be nice to have a default behaviour that: 1...
Add some option to interact during `init` whereby the user would be prompted for a PR title and desc and would have the option to skip it.
We're quite far behind the current LTS version of go (`1.23` as of 2025-01-20) The version of go we're using it `1.16`. https://github.com/Skyscanner/turbolift/blob/d6679f0aec110e2345a5718f50707a1b6def3635/go.mod#L3 https://github.com/Skyscanner/turbolift/blob/d6679f0aec110e2345a5718f50707a1b6def3635/.github/workflows/codeql.yml#L17 https://github.com/Skyscanner/turbolift/blob/d6679f0aec110e2345a5718f50707a1b6def3635/.github/workflows/release.yml#L20 https://github.com/Skyscanner/turbolift/blob/d6679f0aec110e2345a5718f50707a1b6def3635/.github/workflows/test.yml#L18