Closed akash1810 closed 6 months ago
We have three GitHub workflows relating to Scala Steward:
dep-updates_set-automerge.yml
dependency-updates
dep-updates_tracking-branch.yml
main
dep-updates_pr-tracking-branch-to-default.yml
The effect of this is we get one mega-PR each month with all the Scala Steward changes batched together.
This is now redundant following an upstream update to Scala Steward which natively batches changes.
We no longer need our custom version, so remove the workflow files.
Similar to https://github.com/guardian/prism/pull/716.
What does this change?
We have three GitHub workflows relating to Scala Steward:
dep-updates_set-automerge.yml
auto-merging in PRs to thedependency-updates
branchdep-updates_tracking-branch.yml
keeping thedependency-updates
branch up to date withmain
dep-updates_pr-tracking-branch-to-default.yml
running once a month, to open a PR against main with all the changes fromdependency-updates
The effect of this is we get one mega-PR each month with all the Scala Steward changes batched together.
This is now redundant following an upstream update to Scala Steward which natively batches changes.
We no longer need our custom version, so remove the workflow files.
Similar to https://github.com/guardian/prism/pull/716.