Clean up erroneous WordPress releases and branches

Over time, some erroneous WordPress releases or branches were accidentally created:

  • 5.4-RC3-47470. This should have been a nightly bump instead.
  • 4.9.8-beta1-43498. This too should have been a nightly bump.
  • 4.2.26 branch on git:// mirror. This should have been a tag instead, and is already deleted on CoreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. 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 released code are all centrally managed through SVN., but still exists in the 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. mirror and shows up on GitHubGitHub 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 be the repository owner.

Would it be possible to clean them up to avoid confusion?

#git #prio3