[02:31:34] *** Quits: extorr (extor@unaffiliated/extor) (Remote host closed the connection) [02:31:52] *** Joins: extorr (extor@unaffiliated/extor) [03:18:17] *** Joins: skjkrr (uid440352@gateway/web/irccloud.com/x-lfliasrgjkuiozna) [05:27:56] *** Quits: skjkrr (uid440352@gateway/web/irccloud.com/x-lfliasrgjkuiozna) (Quit: Connection closed for inactivity) [09:59:49] hi kazer [10:00:18] what about move from CircleCI to Github Actions? as both are Docker based it should be smooth sailing [10:00:43] CircleCI has problems with PRs on forks for quite a while [11:38:04] *** Quits: genesis (~genesis@unaffiliated/genesis) (Remote host closed the connection) [11:47:21] *** Joins: genesis (~genesis@unaffiliated/genesis) [11:47:21] *** ChanServ sets mode: +v genesis [15:04:34] Hi everyone [15:30:00] i have to say that i haven't really looked into github actions [15:30:06] what issues are we seeing on forks? [15:31:05] on Pull requests from frorks the build never finishes and reports back to the github checks so its not mergeable without admin rights [15:31:50] i am already working on the yml file for github actions, currently testing localy with https://github.com/nektos/act [15:32:24] current version: https://gist.github.com/jkoan/00c75c37b36cb0d842997f5656f4673c [15:32:42] github also offers windows and macos builders [15:32:52] and for public repos totally free [15:33:58] it will also fix some less important issues such as doc changes generated new build of every platform even through only a doc rebuild would be necessary [15:34:38] https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions is the main reference. on..paths will be quite handy [15:38:45] even the release flow can be automated :D https://github.com/actions/upload-release-asset [15:52:01] sanitycheck already working ;-) [16:42:40] nice! [16:44:02] android currently has problems (using circleci docker image) [16:46:53] but if i get everything working like its now you dont have a concern about github actions? [17:09:53] no concerns no. it might just be annoying for people using forks (including me) if everybody has to update their workflow. so we should be mindful of that [17:11:24] for updating its actually as easy as pull the last changes from upstream. For the Workflow, it should be more easy as everything is then on one plattform [19:16:26] well forks can have customized circleci builds. so i think that we might want to make that a gradual change [19:33:05] thats possible with github actions as well [19:33:32] also forks dont need to delete there circleci config [22:12:09] *** Quits: extorr (extor@unaffiliated/extor) (Remote host closed the connection) [22:12:29] *** Joins: extorr (extor@unaffiliated/extor) [23:16:57] *** Quits: extorr (extor@unaffiliated/extor) (Remote host closed the connection) [23:17:19] *** Joins: extorr (extor@unaffiliated/extor)