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 commands that could break/rewrite the history
  • What are the privacy implications for honestly setting Git's and values?
  • composer dump autoload and git
  • Are git repositories copyable?
  • Git clone on Mac with HTTPS not working
  • How does one copy commits without producing different SHA1s?
  • Thanks for every suggestion.

  • Can gitconfig options be set conditionally?
  • Git - take a code, branch it and push partially
  • Are there Git workflows for rolling release web applications?
  • What can I do with Git corruption due to a missing object?
  • Should I store a database backup used for our automated tests in git?
  • Best Way to Develop a Composer Package
  • 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.