Apply to a new repository

Add these LabVIEW CI capabilities to another repository. Pick what you want — get an install command and a ready-to-commit bundle.

1. Your repository

Where to install. Required for the one-click install; the command-line option can also infer it from your git remote.

GitHub supports the browser pull-request install flow.

Installing to a private GitHub repo? Review the private repo setup notes before creating the token.

Fixed to LabVIEW 2026 — the container images and tooling are built for it.

Linux container jobs are selected by default and use the shared Linux worker when dependencies are baked into the image.

2. Capabilities

Customize capabilities Defaults are recommended

Stable and advanced capabilities are selected by default. Experimental features are off unless you opt in. Your project's VIPC/Dragon dependencies are not baked in during install — applying them is a separate, opt-in step you run afterward.

3. Install

Let the configurator open a pull request that adds these files to your repository — and, if you like, link it from your README and switch on GitHub Pages so the dashboard publishes itself. Nothing to download, unzip, or commit by hand. The first time, you paste a fine-grained token; the panel walks you through creating it with the permissions pre-filled. It stays in this browser so you don’t have to paste it again.

Other ways to install (command line or download)

Run this in a local terminal on your computer, from the root folder of a cloned repository. It only writes files into your working tree — review with git diff before committing.

  1. In GitLab or GitHub, copy the repository clone URL.
  2. On your computer, open Terminal, Git Bash, or PowerShell.
  3. Run git clone <clone-url>, then cd <repo-folder>.
  4. Paste the command below in that terminal window.
  5. Review with git diff, then commit and push.
macOS / Linux / Git Bash
Windows PowerShell

          

          

            
            
            
          

        

      

    


    

      
4. Finish setup

      
    
        
  1. Merge the install pull request — the dashboard publishes itself from that merge (no CI run required), and the README link lands in the same merge.
    2. 
        
  2. Enable GitHub Pages from the gh-pages branch (Settings › Pages).
    3. 
        
  3. Set Workflow permissions to Read and write (Settings › Actions › General).
    4. 
        
  4. Optionally pin settings as Actions variables (shown after you choose options).
    5. 
        
  5. Open a pull request that changes a VI whenever you want the analysis columns (VI Analyzer, VIDiff, Mass Compile) to fill in — a failing check never keeps the dashboard from publishing.
    6. 
      

      
None of these choices are permanent — change the LabVIEW version, platforms, activities, and container dependencies any time from ⚙ Configure Pipeline on the dashboard (it opens a pull request with your changes). To pull later tooling improvements, re-run the installer with --update.