Łukasz Wawrzyk
Łukasz Wawrzyk
Depending on platform, user should be able to specify for example which reviwers, labels and milestones to assign to PRs created by Bazel Steward.
It may highly depend on packaging ecosystem, but if we can get changelog for a library, it is good to include all changes that user applies to their repository when...
By default we create and maintain 1 PR per version update. We should allow users to customize this, for example grouping updates of specific dependencies together, minor/patch updates in one...
Users should be able to opt in for automatic PR merging if all checks pass. Scala Steward uses mergify. We may use this or different approach. Most likely it is...
Commit message for dependency update should be configurable with a template. Default template would be "Update {dependency} to {versionTo}". We may consider what variables for template will be provided. We...
Bazel Steward by default creates PRs against default branch (main/master). Users should be able to pick different branch than default, for example, default branch is `main`, but bazel-steward should work...
This issue is about a corner case when someone has, say, metamonorepo, i.e. one git repository contains multiple Bazel projects. Each project would be treated separately, with separate config. Users...
Currently we are just running bazel steward on an existing cloned repository. We could wrap this logic and execute it multiple times on different repositories (first cloning them). This is...