We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.x
SBT now supports version patterns like + 2.13.x. This means ci.yml and .mergify.yml have to be updated much less frequently.
+ 2.13.x
Although, perhaps that makes sbt-github-actions somewhat less necessary
The text was updated successfully, but these errors were encountered:
Actually a much more compelling reason, for anyone using sbt-mergify-github-actions or https://github.com/typelevel/sbt-typelevel/tree/series/0.4/mergify, is that PRs that change .mergify.yml will not be automatically merged be Mergify. If more PRs do not require updating .mergify.yml then more PRs can be merged automatically.
sbt-mergify-github-actions
.mergify.yml
Sorry, something went wrong.
One way or another this is super annoying.
Is anyone maintaining this?
I'm pretty swamped but if I'd contribute this would it get merged and released?
One way or another this is super annoying. Is anyone maintaining this? I'm pretty swamped but if I'd contribute this would it get merged and released?
I'm a maintainer, don't have that much time currently to implement this myself but I am happy to review a PR and merge + release
No branches or pull requests
SBT now supports version patterns like
+ 2.13.x
. This means ci.yml and .mergify.yml have to be updated much less frequently.Although, perhaps that makes sbt-github-actions somewhat less necessary
The text was updated successfully, but these errors were encountered: