You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There are something like ~48 Scala libraries at the Guardian, and ideally those projects will all be either using gha-scala-library-release-workflow, or archived - we don't want to confuse devs by leaving any other patterns to follow!
Follows the instructions to enable the scala lib release workflow janus-app#416 - library project is a sub-project alongside an app. This is OK so long as there's only 1 applicable version number for any library projects in the repo, it would get confusing if you were trying to release 2 different libraries with different version numbers in the same repo.
These are repos that will either provide useful challenges we can learn from, or that will be good for introducing another group of devs to the workflow (eg where adoption is currently low):
There are something like ~48 Scala libraries at the Guardian, and ideally those projects will all be either using
gha-scala-library-release-workflow
, or archived - we don't want to confuse devs by leaving any other patterns to follow!Already updated
Useful repos for adoption
These are repos that will either provide useful challenges we can learn from, or that will be good for introducing another group of devs to the workflow (eg where adoption is currently low):
Repos not yet converted
The text was updated successfully, but these errors were encountered: