![Git Tip: Find All Changed Files](/content/images/size/w600/2024/06/Screenshot-from-2024-06-20-13-12-47.png)
SCC
A collection of 29 posts
![Git Tip: Find All Changed Files](/content/images/size/w600/2024/06/Screenshot-from-2024-06-20-13-12-47.png)
![Git SubModules and GitLab CI](/content/images/size/w600/2023/05/Screenshot-from-2023-05-29-23-06-15-1.png)
![The Absolute Easiest Way to Setup LVCompare and LVMerge](/content/images/size/w600/2023/01/lvdiff-min-1024x576.png)
![Using Git Hooks](/content/images/size/w600/2022/11/image_2022-11-08_141748607.png)
![Latest Version of Git Broke LVCompare Usage](/content/images/size/w600/2022/07/image-1.png)
![Checking for New GitLab Releases](/content/images/size/w600/wordpress/2021/12/GitLab-Autoversion-5.png)
Checking for New GitLab Releases
In my previous posts, I talked about automatic versioning and automatically creating releases. The next step is to create auto-updating code. By auto-updating I don’t mean code that automatically updates behind your user’s back ala Windows 10. You can do that if you want, but I believe the
![Automating Gitlab Releases](/content/images/size/w600/wordpress/2021/12/image_2021-12-06_170052-5.png)
![Automatic Versioning](/content/images/size/w600/wordpress/2021/12/Versioning-Ideal-6.png)
Automatic Versioning
At the GLA Summit recently minted LabVIEW Champion Felipe Pinheiro Silva gave a 7×7 on versioning. It was interesting. Be sure to take a few minutes and watch it when the video is released. I do things slightly differently. I learned my method from another LabVIEW Champion, Stefan Lemmens.
![A Better Way To Set Up LVCompare and LVMerge](/content/images/size/w600/wordpress/2021/04/image_2021-04-19_172222-5.png)
A Better Way To Set Up LVCompare and LVMerge
EDIT: Since I originally wrote this post, I have come up with a much easier way. I am leaving this post up for historcial reasons, but do yourself a favor and just go here
I have previously written about setting up LVCompare and LVMerge. I ran into a situation where
![April 2021 Webinar](/content/images/size/w600/wordpress/2021/03/2021-03-11_12-08-47-5.png)
![LazyGit](/content/images/size/w600/wordpress/2021/02/image_2021-02-02_095439-5.png)
![View the Git Reflog Graphically](/content/images/size/w600/wordpress/2021/02/image_2021-01-29_115518-5.png)
View the Git Reflog Graphically
While creating some content for my “Using Git Effectively” course, I discovered something new and amazingly useful. You may know about Git’s reflog and that it provides a chronological history of where your HEAD has been so that you can recover orphaned commits.
For some things though, it can
![Showing Status in the Git Bash Prompt](/content/images/size/w600/wordpress/2020/12/Git-Bash-5.png)
![Continuous Integration vs Feature Branches](/content/images/size/w600/wordpress/2020/11/pexels-iconcom-216695-1-5.jpg)
Continuous Integration vs Feature Branches
After reading the Continuous Delivery Book, I have been thinking a lot about branching strategies and Continuous Integration versus Feature Branching. I put together this little chart of the pros and cons of each.
Feature BranchingContinuous IntegrationTrustDoes not require trust. You can control via GitLab who can merge into main
![Fowler's Branching Patterns](/content/images/size/w600/wordpress/2019/12/git-model@2x-5.png)
Fowler's Branching Patterns
Martin Fowler is prolific writer about software development. One of his more well-known books is probably Refactoring. He also has a blog with lots of good content. After reading the Continuous Delivery book and working on my Using Git Effectively course, I have been thinking a lot about branching strategies.
![Branch by Abstraction](/content/images/size/w600/wordpress/2020/11/Blank-diagram-Add-Generic-5.png)
![Oh Shit Git](/content/images/size/w600/wordpress/2020/09/Screenshot-from-2020-09-21-12-22-47-5.png)
![Undoing A Bad Commit](/content/images/size/w600/wordpress/2020/08/git-reset-head-5.png)
![Setting up LVCompare and LVMerge](/content/images/size/w600/wordpress/2020/07/lvdiff-min-5.png)
![Automatically Creating A Gitlab Repo](/content/images/size/w600/wordpress/2020/07/gitlab-new-5.png)
Automatically Creating A Gitlab Repo
I’ve been working on streamlining some of my processes lately. I noticed that one of the one things that takes a little time is creating a new GitLabRepository. It just seemed like it took too much time.
Here are the previous steps
1. Goto GitLab Webpage
2. Login
3.
![SSH keys and git bash](/content/images/size/w600/wordpress/2020/07/ssh-5.png)
![Changing Git's default branch](/content/images/size/w600/wordpress/2020/06/BLM-5.png)
![Git Reflog](/content/images/size/w600/wordpress/2020/06/reflog-5.png)
![Navigating a git repository](/content/images/size/w600/wordpress/2020/06/Commit-Graph-a2114-5.png)
![Git For Teams](/content/images/size/w600/wordpress/2020/06/GFT-5.jpg)