Running on Java 19-ea+23-1706 (Preview)
Home of The JavaSpecialists' Newsletter

2.11 Committing Our Changes to Git

Juppies 2 by Dr Heinz M. Kabutz

We commit our changes to our local source control repository. It is a good idea to commit often. If we have a lot of commits, we can squash them into a single commit once we have completed all our work (if we wish to). Saving our work regularly helps to keep a history of what we have achieved recently. It is a bit like playing a tricky computer game and saving our progress regularly. In case we take a wrong turn, we can roll back as far as we would like to.


When you load these comments, you'll be connected to Disqus. Privacy Statement.

Table of Contents

We hope you enjoyed this tutorial. If you did, you will also enjoy our courses. We suggest you start with Extreme Java - Advanced Java, followed by Extreme Java - Concurrency Performance for Java 8.

About the Author

Heinz Kabutz Java Conference Speaker

Java Champion, author of the Javaspecialists Newsletter, conference speaking regular... About Heinz

Superpack '22

Superpack '22 Our entire Java Specialists Training in one huge bundle more...

Free Java Book

Dynamic Proxies in Java Book
Java Training

We deliver relevant courses, by top Java developers to produce more resourceful and efficient programmers within their organisations.

Java Consulting

We can help make your Java application run faster and trouble-shoot concurrency and performance bugs...

Java Emergency?

If your system is down, we will review it for 15 minutes and give you our findings for just 1 € without any obligation.