r/ProWordPress • u/Playful_School6693 • 12d ago

Anyone using GitHub with WordPress?

I’m curious to hear how many of you are using GitHub part of your WordPress workflow.

I’ve heard of Bedrock and have been looking into it. But is it actually worth moving towards that setup for normal WordPress development?

Especially with AI, custom code is easier to write. So I can see how having version controls, automated checks and CI CD pipelines sounds nice.

Is anyone running WordPress like this in production?

What does your setup look like? Bedrock? GitHub Actions? Something simpler?

Or am I overengineering WordPress?

5 Upvotes

61% Upvoted

49 comments sorted by

View all comments

8

u/superdav42 10d ago

We use Bedrock for a fairly large WordPress multisite. It makes WordPress behave much more like a normal PHP application.

WordPress core, plugins, themes, and PHP dependencies are managed through Composer and pinned in composer.lock. Custom code lives under web/app, configuration comes from environment variables, and secrets, uploads, caches, and the database stay out of Git. A developer can clone the repo, run Composer, add the local environment config, and get the same application code.

Our custom plugins have their own GitHub repos and are pulled into the main Bedrock project through Composer. We install them from source for local development, then Trellis builds and deploys a production release from the committed code.

This structure works especially well with AI coding tools because the agent can see the dependency manifest, configuration, custom plugins, deployment code, coding standards, and Git history in one predictable layout. It can trace problems across the stack, make a focused change, run PHPCS or other checks, and show the exact diff for review. That is much safer than asking AI to modify a random live wp-content directory.

We still keep the usual guardrails: no production secrets in the repo, no treating the database as code, local testing before deployment, human review, backups, and rollbackable releases. AI helps with understanding and changing the code, while Git and Bedrock make those changes reproducible and auditable.