Optional automerge action for scala-steward PRs

[joroKr21]

Would there be interest in adding an optional automerge action for scala-steward?

• Could use for example https://github.com/marketplace/actions/merge-me
• There is also Mergify but idk if it can run as a GitHub action

[djspiewak]

It's definitely doable, I'm just not sure it belongs here. Doesn't mergify meet the criteria? I haven't actually played with it too much.

[joroKr21]

I'm not sure either. But it's definitely something that a lot of Scala libraries could benefit from and save some precious maintainer time. Depends on the goals of this plugin.

[joroKr21]

@djspiewak how do you regenerate the test files?

[nafg]

One issue I see with mergify is that apparently you have to specify every matrix permutation like this:

https://github.com/http4s/http4s/blob/main/.mergify.yml

Since the job name includes the minor scala version, this means the mergify file will get invalidated quite often.

Is there a way to make the job names less specific?

[joroKr21]

I opened a PR with https://github.com/marketplace/actions/merge-me which is a GitHub action unlike Mergify

[djspiewak]

Is it possible to use wildcards in the matrix definition? I see some above in the labels.

[joroKr21]

This is happening in typelevel/sbt-typelevel#190

[nafg]

You could have just used sbt-mergify-github-actions from https://github.com/nafg/mergify-yaml/. I mentioned it above

[joroKr21]

I think sbt-typelevel solves the issue you mentioned about the matrix

[nafg]

As does my library