Optional automerge action for scala-steward PRs about sbt-github-actions HOT 10 CLOSED

As does my library

from sbt-github-actions.

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.

from sbt-github-actions.

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.

from sbt-github-actions.

@djspiewak how do you regenerate the test files?

from sbt-github-actions.

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?

from sbt-github-actions.

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

from sbt-github-actions.

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

from sbt-github-actions.

This is happening in typelevel/sbt-typelevel#190

from sbt-github-actions.

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

from sbt-github-actions.

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

from sbt-github-actions.