Looking at some other issues here related to automating releases / enforcing certain checks it is clear that we will need some common ci solution for all of these.
I would usually go for circle, but have recently switched my personal projects to GitHub actions and thus far only limitation there was that Docker can't run macOS environment.
Otherwise, process is very simple and creating your own actions doesn't take much effort either.
Hence I thought about proposing this for repos within React Native Community (At least some of them that don't have CI yet?).
We could create new repository here that could house custom actions created by the community, so they are easily accessible to every maintainer as well ass have examples for different workflows, including main one that community might accept as a standard?
Utalising these will mean we can easily add things like Danger since we won't need to fiddle with github permission token generation (actions expose one as default secret), nor will we need to set up each repo on a third party ci service.
What do you guys think? If this is interesting it might be worth to enrol react-native-community into Github Actions Waiting list (if it is not there yet) https://github.com/features/actions
Looking at some other issues here related to automating releases / enforcing certain checks it is clear that we will need some common ci solution for all of these.
I would usually go for circle, but have recently switched my personal projects to GitHub actions and thus far only limitation there was that Docker can't run macOS environment.
Otherwise, process is very simple and creating your own actions doesn't take much effort either.
Hence I thought about proposing this for repos within React Native Community (At least some of them that don't have CI yet?).
We could create new repository here that could house custom actions created by the community, so they are easily accessible to every maintainer as well ass have examples for different workflows, including main one that community might accept as a standard?
Utalising these will mean we can easily add things like Danger since we won't need to fiddle with github permission token generation (actions expose one as default secret), nor will we need to set up each repo on a third party ci service.
What do you guys think? If this is interesting it might be worth to enrol react-native-community into Github Actions Waiting list (if it is not there yet) https://github.com/features/actions