Closed imballinst closed 2 years ago
Github Actions is pretty good ;)
I'm a bit confused about 1, what are you trying to test?
@KapitanOczywisty yes, but it's only for master
, isn't it? We can't run GitHub Actions on non-master branch (last I checked).
As for (1), it's about what you said earlier about updating lib
. It's technically to ensure that lib
is always up to date (e.g. so that I don't mistakenly publish a version with stale lib
folder).
@KapitanOczywisty yes, but it's only for
master
, isn't it? We can't run GitHub Actions on non-master branch (last I checked).
I've never heard about that, but even If it was the case in the past, it's not anymore.
As for (1), it's about what you said earlier about updating
lib
. It's technically to ensure thatlib
is always up to date (e.g. so that I don't mistakenly publish a version with stalelib
folder).
Right. I've seen somewhere lately build auto committed on reviewed pull-request. Basically you're setting label automerge
etc and Actions will build, commit and merge PR. Probably: https://github.com/EndBug/add-and-commit + https://github.com/pascalgn/automerge-action
Previously we have this TravisCI thing, but since its migration, the hook couldn't work and hence I disabled it. I'll probably need to do 2 things:
yarn build
updates a new file ingit status
. If it has new untracked files, then fail the build.master
branch.