- 🧩 Key Components
- 🚀 Getting Started & Contributing
- 🌱 Feature & Experiment Workflows
- 📚 Documentation
- 📄 License & CLA
- 💬 Contact & Discord
The LabVIEW Icon Editor is an open-source, MIT-licensed project that releases VI Packages with the latest community-driven features. When LabVIEW is built for an official release, it automatically pulls the latest version of the Icon Editor from this repo’s main branch—currently targeting LabVIEW 2026 Q1.
This means that your contributions—whether features, fixes, or docs—can ship with official LabVIEW distributions.
- 🛠 Built entirely in G
- ⚙️ GitHub Actions orchestrate PowerShell-based CI workflows for testing, packaging, and publishing
.vipartifacts - 🔁 This project pioneered CI/CD pipelines, documentation, and foundational infrastructure that will eventually migrate to a centralized dependency repository so that it can expand along with other concepts (e.g. lvenv)
NI’s Open Source Program encourages community collaboration to evolve and improve this tooling that streamlines the way the LabVIEW community tests NI-governed features.
Prerequisites:
• LabVIEW 2021 SP1 or newer
- Download the latest
.vipfile from the releases page. - Open VIPM in Administrator mode.
- Install by double-clicking the
.vipfile or opening it via File ▶ Open Package in VIPM. - Verify the installation by creating a new VI and opening the Icon Editor.
-
Source Files
- VI-based.
-
PowerShell Automation
- Built on G-CLI
- Supports repeatable builds, releases, and CI tasks
- Easy to use in local or GitHub-hosted runners
-
CI/CD Workflows
We welcome both code and non-code contributions—from bug fixes and performance improvements to documentation or testing.
- 📑 CLA Required – External contributors must sign a Contributor License Agreement before we can merge your pull request.
- 🧭 Steering Committee – A mix of members of LabVIEW R&D and community volunteers who guide roadmap and merge authority.
- 🔄 Issues & Experiments – Look for issues labeled “Workflow: Open to contribution”.
- 🧪 Long-Lived Features – For experimental branches, see EXPERIMENTS.md
More contribution info is in CONTRIBUTING.md.
-
Discuss or Propose an Issue
- Use GitHub Discussions or Discord
-
Assignment
- Once approved by LabVIEW R&D, issue is labeled Workflow: Open to contribution
- A volunteer comments on the issue in order to get assigned
- NI Maintainer creates a feature branch and assigns the issue
-
Branch Setup
- Fork + clone the repo
- Checkout the feature branch and implement your changes
-
Build Method
- Choose either:
-
Submit PR
- CI will build and publish a testable
.vip - Reviewers verify and collaborate with you until it’s ready
- CI will build and publish a testable
-
Merge & Release
- Merges go to
develop, then tomainduring the next release cycle
- Merges go to
- Used for large or multi-week features
- Docker VI Analyzer & CodeQL run automatically
- Manual approval required for
.vippublishing (approve-experimentevent) - Sub-branches for alpha/beta/RC are optional
More info in EXPERIMENTS.md
Explore the /docs folder for technical references:
- 📦 Build VI Package
- 🧪 Development Mode Toggle
- 🚢 Multichannel Release Workflow
- 🖥 Runner Setup Guide
- 🧬 Injecting Repo/Org Metadata
- 🧯 Troubleshooting & FAQ
- 🔬 Experiments
- 🛡️ Maintainers Guide
- 🧱 Troubleshooting Experiments
- 🏛️ Governance
- MIT License: LICENSE
- Contributor License Agreement: Required before we can merge your contributions
By contributing, you grant NI the right to distribute your changes with LabVIEW.
- 🗨 Discord Server – ask questions, propose ideas, get feedback
- 📂 GitHub Discussions – for formal proposals or workflows
Your ideas, tests, and code shape the Icon Editor experience across LabVIEW 2021–2026 and beyond.