Microsoft Is Said to Have Agreed to Acquire Coding Site GitHub – Bloomberg

Microsoft Is Said to Have Agreed to Acquire Coding Site GitHub – Bloomberg https://www.bloomberg.com/news/articles/2018-06-03/microsoft-is-said-to-have-agreed-to-acquire-coding-site-github

If this is true, and we’ll know soon enough, it changes the landscape for open source software development. The acquisition may be behind the GNOME project’s decision to move to GitLab, an open source alternative to Gitub.

It’s worth mention that git and GitHub are not the same thing. There will almost certainly be stories floating around that MSFT is buying git, but that isn’t the case. GitHub is just the must popular of several web based front ends to git.

How to recover dropped data from stash | Opensource.com


First a warning: When you are implementing a big feature, split it in small pieces and commit it regularly. It’s not a good idea to work for a long time without committing your changes.

Source: How to recover dropped data from stash | Opensource.com

Git can save your bacon, but nothing beats applying the “saving frequently and often” approach. Commit frequently and often, stash sparingly, branch as necessary, push always.

VersionPress Brings the Power of Git to WordPress

One of the best things about WordPress is how easy it is to make sweeping changes to a website in just a few minutes. But with no easy way to revert a website to a previous state, you can lose a lot of work very quickly if you aren’t careful. VersionPress brings the power of Git to WordPress so you can make as many changes as your want with the knowledge that undoing any change is just a click away.

Source: Setting Up VersionPress for Git-Powered WordPress Version Control – WPMU DEV

Appears to work for both content and backend changes which would be handy. Not sure how it would work on large multisite installs like Classcaster or Lawbooks.

GitHub adds commit squashing to tidy up your commit history

Commit squashing has the benefit of keeping your git history tidy and easier to digest than the alternative created by merge commits. While merge commits retain commits like “oops missed a spot” and “maybe fix that test? [round 2]”, squashing retains the changes but omits the individual commits from history. Many people prefer this workflow because, while those work-in-progress commits are helpful when working on a feature branch, they aren’t necessarily important to retain when looking at the history of your base branch.

Squash your commits – GitHub

New feature allows for cleaner commits in your code and more suitable for a broader range of workflows.