> Apart from that, I would recommend to not build new images on each push to > PRs or master branch.
Yes thats why I suggest a different repository, its separate, so like Geany plugins doesn't get rebuilt with every Geany PR. Plus the points @kugel- noted. Now github allows transferring issues I just slide Mac ones to that repository. > Additionally, when Travis CI is used, you'll probably running out of free > credits quickly. Migrating to Github Actions could be a solution Agree it should use Github actions if being in the Geany organisation uses Geany Travis credits. That should happen before the repository is migrated. > I'm going to propose this also for the Geany repositories. Another issue, but agree it should be examined/tested. > Despite the general perception, technically it makes no difference and might > be even a wrong suggestion to the user. True, and at the moment the @ecmu scripts wget stuff from all sorts of places, that needs to become traceable if users are to be able to trust the resulting appimage. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/1303#issuecomment-943848392
