LocalWP and VScode Github Repository

#Hello Guys,

Hello,

I’m not a WordPress developer, but I set up websites for a few clients. However, I sometimes need to work with my teammates, so I want to use GitHub.

Which folders and files of the WordPress website I created in LocalWP do I need to push to GitHub? If I push the entire WordPress core, it might conflict with the files on CloudHosting. I only want the theme, plugins, and the pages, texts, and images that I’ve changed to be in the repo. Similarly, I want my teammates who have permissions on the repository to be able to work together on the same repo, even if it’s not real-time, by pulling it to their locals.

I want to open the WordPress site I created with VScode and push it to GitHub from there.

Thanks for answers,

Hey @cayci – Welcome to the Local forums!

There isn’t one “correct” way to do this, mostly because each team and hosting provider recommends different work flows.

We do have this help doc that you might read for some inspiration:

Personally, I’m a fan of having git repos be smaller, and targeted to each “thing,” for example, a repo for a custom theme and a repo for a custom plugin. But other teams like to track the whole WordPress installation. I don’t typically like doing that because once you start adding other third-party plugins, it become tedious to track updates to those themes within the site-level git repo.

As for the VS Code part, I usually recommend opening VS Code at the “public” folder so that it’s easier for it to navigate code and jump to function definitions.

Anyway, hope that helps jump-start your thinking and finding a workflow that works for you!

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.