Rules to set base branch

[nafg]

For instance, Slick is currently built on Java 11, but a number of dependency updates require newer Java versions. Rather than disabling them and reenabling them in the future when the minimum Java version is bumped on the main branch, it might be nice to have a Java X branch and Scala Steward will target some dependencies for that base branch.

[bpholt]

I think you can change the targeted branch using Foo/bar:branch in the repos.md file. IIUC, Scala Steward will use the .scala-steward.conf file on the targeted branch, so you have the ability to customize the behavior on the branch. Would that do what you need?

[nafg]

Meaning I can have the same repo twice but with s different branch? Yes I think that would probably work

[nafg]

On second thought, I think this would be terrible. Wouldn't that basically default to duplicating every PR unless explicitly excluded? Like if I have main and java17 branches (maybe more), N entries in repos.md means N times every PR except where excluded, no?

Of course if a dependency update is applied to main I want it applied to java17 too, but a better way to do that is to periodically update java17 from main. Having PRs multiply like that I think would be too annoying.

[bpholt]

Yes, exactly. That's what we do, put the repo in the list once for each branch. It does send multiple PRs but you could configure each branch so that it only manages the dependencies that are specifically relevant to the branch. 🤷🏻‍♂️

[nafg]

At least it should let me modify the base branch after Scala Steward opens it. Currently if I do that, IIRC Scala Steward will not count it and it will open a new PR.