Meta Environment Now Supports Contributing with Git

The Meta Environment has always managed its coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. functionality in GitGit Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency. Git is easy to learn and has a tiny footprint with lightning fast performance. Most modern plugin and theme development is being done with this version control system. https://git-scm.com/., but up until now, it used SubversionSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. to check out the actual files that make up each MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. website. New contributors are much more likely to be familiar with Git than SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/., though. Requiring them to learn SVN in addition to all of  our other tools and processes introduced an unnecessary burden.

The goal of the Environment is to help make contributing as easy as possible, so it makes sense to switch to Git instead. As of today, that switch is complete, and new installations will use Git automatically.

The two exceptions are: 1) Any pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party or theme that doesn’t have an official Git mirror; 2) the entire translate.wordpress.orgWordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/ site, since it’s in the process of migrating to GlotPress 2. In those cases, SVN is still used.

If you have an existing installation, it will continue to use Subversion until you git pull the latest copy of the Environment, and run vagrant provision. During that provision, each site’s public_html folder will be backed up to public_html-old-svn-backup, and a new Git-based public_html folder will be provisioned. If you’re working on any unfinished patches, just copy the modified files from the old directory to the new one.

If you’d like to learn more about contributing with Git, check out this guide from the Meta Handbook:

Contributing With Git

#wordpress-meta-environment