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
bump github actions, regenerate ci.yml #75
Conversation
Note scala steward is now able to auto regenerate the github workflow as part of the upgrade PR. So we shouldn't need to do this anymore. |
Cool! |
I need to learn how to add custom rules like that. Are they ad-how or is there some system for it? |
@johnynek It will do it automatically on the next update of sbt-github-actions. There is nothing you need to do to enable it. The PR will then look like this scala-steward-org/test-repo-2#10. |
These hooks are added directly to |
@fthomas That's great! but I mean in general, there are libraries or tools that need some special migration. I'm more interested in how those kinds of things are added in the general case. |
looks like it is still ad-hoc, but you can imagine declaring in some jar some code that should be run to update the repo... but it is challenging to imagine the security issues, etc... |
Right, it would be great if libraries and plugins would ship with this information so that multiple tools could use it and more maintainers would provide it. The same applies for Scalafix migrations. My hope is that the experience in Scala Steward with post-update hooks and Scalafix migrations can help designing such facility. |
An example is that I would really like to also get this functionality for sbt-spiewak upgrades (since it brings in sbt-github-actions as an upstream dependency), but it would be unreasonable for scala-steward to hard-code all of that for increasingly niche plugins. Better if there were some way for me to publish it ourselves. |
I don't mind adding hooks for niche plugins to Scala Steward until there is a general solution. If you want to run
Agreed. I'll open an issue in scala-steward for further discussion. |
replaces #71
we needed to rerun to build ci.yml.