Maintenance of the GitHub mirror of the WordPress build repository has recently being transferred to the WordPress.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/ systems team.

In future, any syncing issues with the GitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged by the repository owner. https://github.com/ mirror should be reported to the system team, either on the make/systems blog (versus network, site) of via the Slack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/ #meta channel if you are unable to post a report to the systems blog.

The WordPress git mirror began as an unofficial project maintained by Mark Jaquith an Emeritus Committer A developer with commit access. WordPress has five lead developers and four permanent core developers with commit access. Additionally, the project usually has a few guest or component committers - a developer receiving commit access, generally for a single release cycle (sometimes renewed) and/or for a specific component. and WordPress Lead Developer. In 2014 official Git mirrors were created and mirrored to GitHub.

The original GitHub mirror of the build repository continued to be maintained by Mark as it used a different branch A directory in Subversion. WordPress uses branches to store the latest development code for each major release (3.9, 4.0, etc.). Branches are then updated with code for any minor releases of that branch. Sometimes, a major version of WordPress and its minor versions are collectively referred to as a "branch", such as "the 4.0 branch". and tag A directory in Subversion. WordPress uses tags to store a single snapshot of a version (3.6, 3.6.1, etc.), the common convention of tags in version control systems. (Not to be confused with post tags.) naming structure to the official mirror along with different hashes.

Although Mark is no longer active in the project, until recently he has continued maintaining the mirror single handedly. The move to systems will increase the number of people maintaining the sync.

Thank you @markjaquith for maintaining the mirror since you stopped being active in the project day-to-day.

Props @barry and @jorbin for reviewing this post prior to publication.

#git, #github