Are there any benefits of this move? From my point...
# chuckerv
Vova Buberenko
02/26/2020, 8:14 AMAre there any benefits of this move? From my point of view it might be eventual switch to Github Packages for distribution and some additional Actions, which might improve our development flow.
Despite that fact I am not sure that we should do it now.
I would really love to see us finishing some features and PRs (like https://github.com/ChuckerTeam/chucker/issues/69 ), since they really should be our top priority and do things like switching CIs in the meantime and only if it is worth it.
Vova Buberenko
03/01/2020, 10:41 AM@gammax Also, when you have time, could you, please, provide an answer here?
g
gammax
03/02/2020, 8:05 PMAre there any benefits of this move?(context: I’m migrating several proj. to GH Actions recently). I generally feel that is easier for forks/contributors to have an action running out of the box. Currently we’re on travis .org, and its future is a bit unclear. Moreover, there are several actions that are easy to plug for maintainance of the repo.
From my point of view it might be eventual switch to Github Packages for distribution and some additional Actions, which might improve our development flow.On GH Packages, that seems really interesting. The point is that so far setting up a dependency hosted on GH Packages, requires to setup an extra maven repository 😕 On this side I’m actually more to have JitPack for development and have artifacts also on MavenCentral. As a side note: our artifacts are not signed. With Gradle 6.2, users can enable signature verification, so our artifact will not comply (something to keep in mind for the future).