Skip to content
New issue

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

Suggestion: for sbt 1.7, use .x syntax for scala versions #114

Open
nafg opened this issue Jul 12, 2022 · 3 comments
Open

Suggestion: for sbt 1.7, use .x syntax for scala versions #114

nafg opened this issue Jul 12, 2022 · 3 comments

Comments

@nafg
Copy link

nafg commented Jul 12, 2022

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

@nafg
Copy link
Author

nafg commented Jul 17, 2022

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.

@nafg
Copy link
Author

nafg commented Sep 26, 2024

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?

@mdedetrich
Copy link
Contributor

mdedetrich commented Sep 26, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants