Github desktop add submodule1/13/2024 ![]() I will certainly be investigating more Actions on Github to see what else I can automate. And if anything does go wrong, then I can always do a patch via an FTP locally. This seemed faster than doing it locally via FTP. Successful ExperimentĬommit and push that from the github explorer, and it automatically deploys via FTP to the hosting site. github/workflows/main.yml file: on: pushįtp-username: $Īnd setup the secrets through the Github console to see what happens. So I will experiment with an FTP action from a private repo, to see if I can automatically push changes live to my web host when I push the generated site changes to GitHub. And there doesn’t seem to be a pricing level that allows this. The major downside is that you can’t use this as an http server host for commercial organisations. You will now know whether submodules are just pointing at a different commit or if there are changes within them that you must commit. Submodule support just got much better from GitHub Desktop by providing a more detailed diff when they have changes. rather than a project repo, so you would need to create new organisations for every site, which is unsustainable. GitHub Desktop 3.1 improves submodule support and now supports multi-commit diffing. You need a root level site then you need to have an organisation repo e.g.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |