How to retrieve files from github in LabVIEW

[GIC-SAGM]

Hello All.

My question is NOT about using github for source control of vi's or LV projects.

I need to retrieve configuration files from github from within applications (.exe) developed in LabVIEW.

It resembles TestStand loading test sequences that are developed/maintained by a team - except I need this from within my apps because I do need to ensure that I always load "certified latest version" of config files.

As the main problem - and main use use/purpose of github is source control and ci/cd for code - I did not find anything.

Any clues, ideas, help?

Much appreciated.

[Quiztus2 · Accepted solution]

You could use system exec node to execute git commands from within labview.

[GIC-SAGM]

Simple and straightforward, of course, I hoped in a more "elegant" solution.

[GerdW]

Hi GIC,

---

@GIC-SAGM wrote:

Simple and straightforward, of course, I hoped in a more "elegant" solution.

---

Encapsulate the SysExec calls inside our own VIs (library) to provide a "more elegant" solution…

[rolfk]

This is not specifically for github, but simply for programmatic control of git on your system. It's also using the command line and while this may not seem sexy for Windows users (and the creation of a separate process is indeed a bit expensive under Windows), this is by far the most easy way to integrate other tools into your workflow. Under Unix, it is in fact THE standard.

If you want to access github directly you would have to read into what their, most likely REST based, web API is and implement it by using the JKI Rest Web Client library or something along those lines. Most likely this is however a path of pain and regret. Web APIs tend to be not that stable, require always some form of authentication or API key, that may have to be refreshed regularly, and in general will cause your perfectly working solution today to fail next year for unobvious reasons.

[GIC-SAGM]

Thanks Rolf.

Hampel solution seems quite nice.

And you're right, KISS is always the best solution (but, as someone said, not simpler 😉)