Organize LabVIEW in a git repository

I’m forced to work with LabVIEW source code on a Windows 7 machine and am curious what might be the best setup to handle the source code in a remote Git repository.

Currently I’m handling everythin like I would with my C projects, means Git Bash and a simple .gitignore file that excludes .aliases and .lvlps files, but think that there might be some possible improvement.

  • Git pushes to wrong heroku app
  • Keep commit message subject under 50 characters in SourceTree
  • TortoiseGit - change default merge message
  • Is it possible to drop a single file from git stash?
  • Git pull from someone else's fork
  • `hub` pull-request for organization repository
  • Thanks for every suggestion.

  • git subdirectory which is ignored
  • git submodule conflicts during rebase causes commit to disappear
  • Way to show merging status in command line in git
  • switch branch in git by partial name
  • git mergetool --follow?
  • How to track revision history of revision history?
  • 3 Solutions collect form web for “Organize LabVIEW in a git repository”

    If you have LV professional you can get diff and merge to work using

    I use this together with git bash.

    You could look for tips and ideas in the NI Community Group set up just for Git users.

    Well, what answers do you expect?

    If you are searching for another git client, i can recommend you TortoiseGit. Im working with Egit, but thats only for eclipse. Im sure there are a bunch of clients out there, just google it.

    Other than that, Git Bash is fine. It works, why change it? Using another client won’t give you any benefits other than better UI’s.

    Git Baby is a git and github fan, let's start git clone.