Free tools Windows power users keep installed
One-click scans. No signup required.
Use GitHub Actions configuration variables for non-sensitive values you want to reuse across workflows, such as a deployment region or a feature flag. Define them at the organization, repository, or environment level, then reference them with ${{ vars.NAME }}. For values confined to one workflow, use its env block; for passwords, tokens, and other sensitive data, use secrets instead.
Configuration variables, workflow env, and secrets
GitHub distinguishes configuration variables from custom environment variables declared in a workflow. Configuration variables are managed in GitHub and made available through the vars context. Workflow env values are declared in the workflow file and are useful when their scope should be limited to that workflow, job, or step. Both approaches can supply ordinary configuration, but neither makes a value suitable for secret storage.
Configuration variables are rendered unmasked in build output by default. Do not store passwords, access tokens, or other sensitive information in them. GitHub advises: “If you need greater security for sensitive information, such as passwords, use secrets instead.” See GitHub’s explanation of Actions variables.
| Choose | Best fit | How to reference |
|---|---|---|
| Configuration variable | Non-sensitive configuration reused across workflows at organization, repository, or environment scope. | ${{ vars.DEPLOY_REGION }} |
Workflow env |
A value defined in the workflow file and scoped to a workflow, job, or step. | ${{ env.MY_VARIABLE }} in an expression; use the shell’s environment-variable syntax in a script. |
| Secret | Sensitive information such as passwords or tokens. | Use the appropriate secrets context; do not substitute a configuration variable. |
How to define and reference a configuration variable
Create the variable at the scope where it should be managed, then reference it with the vars context wherever that context is supported. For example, a workflow can use ${{ vars.DEPLOY_REGION }} to read a configuration variable named DEPLOY_REGION.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
#1 Best Overall
- Read Before You Buy — No Video Output: These adapters support charging and USB 2.0 data transfer, but cannot transmit video signals. Except for standard USB webcams (which use USB data only), they are not compatible with HDMI/DisplayPort cables, video-capable USB-C hubs, or docking stations with video output.
- Convert USB-A Ports to USB-C: Designed to connect USB-C earphones, cables, flash drives, card readers, and other USB-C accessories to standard USB-A ports. Plug-and-play with no drivers or software required.
- Aluminum Alloy Housing: Built with a sturdy aluminum alloy shell that aids in heat dissipation and protects against daily wear and scratches. Designed to maintain a stable and secure connection.
- Compact & Travel-Friendly: The ultra-compact design allows the adapter to stay plugged into your device without blocking adjacent ports or adding bulk, reducing wear and tear on your original USB ports.
- 12-Month Warranty: Backed by a 12-month manufacturer warranty for peace of mind. Designed to meet strict quality control standards for reliable everyday performance.
For values declared in a workflow’s env mapping, expression contexts use ${{ env.MY_VARIABLE }}. Inside a runner script, use the syntax of the selected shell: for example, $NAME in Bash or $env:NAME in PowerShell. These expression and shell forms apply at different processing stages; they are not interchangeable in every workflow location.
Choose a scope that matches who needs the value
- Organization: centrally manage a value for eligible repositories. An organization variable can have an access policy limiting which repositories may use it.
- Repository: keep a value available to workflows in one repository.
- Environment: associate a value with a deployment environment. Its availability is tied to the job starting, which affects when it can be used.
When configuration variables with the same name exist at multiple scopes, the narrower scope takes precedence: environment over repository over organization. This ordering does not mean an environment-level value is available during every earlier workflow-processing stage; environment variables become available on the runner after the job starts.
Rank #2
- 5-in-1 USB-C Hub: Experience comprehensive connectivity featuring a Power Delivery input, two USB-A 2.0 ports, a USB-A 3.0 port, and an HDMI port. (Note: The USB-C power delivery input port is only for connecting an external wall charger to power your laptop and cannot power peripheral devices.)
- 90W Pass-Through Charging: Achieve optimal charging with 90W pass-through power to your laptop, supported by a total input of 100W, with the hub reserving 10W for operational efficiency. (Note: Wall charger not included.)
- Quick Data Transfers: Accelerate your productivity with rapid data transfers using a high-speed 5Gbps USB 3.0 port and two 480Mbps USB 2.0 ports.
- 4K HDMI Display: Enhance your visual experience with a hub capable of delivering 4K resolution at 30Hz in both mirror and extend modes. Please note that this hub is compatible with MacBook (macOS 12 and newer), Windows 10 and 11, ChromeOS, and laptops equipped with DP Alt Mode and Power Delivery. Note: This device is not compatible with Linux.
- What You Get: Anker USB-C Hub (5-in-1, 4K HDMI), welcome guide, 18-month warranty, and our friendly customer service.
Understand when expressions and shell variables are evaluated
GitHub evaluates workflow expressions at processing points that can occur before a job is sent to a runner. The runner’s environment variables, by contrast, exist during job execution. A shell variable therefore cannot replace a context in an early workflow expression such as an if: condition. Use a context, such as vars, when it is supported at that location.
Context availability depends on the exact workflow syntax location. Check GitHub’s context reference before choosing a context for a job condition, workflow-level setting, or other expression. This is especially important for environment-scoped values, which are not available until the job begins executing.
Rank #3
- Sleek 7-in-1 USB-C Hub: Features an HDMI port, two USB-A 3.0 ports, and a USB-C data port, each providing 5Gbps transfer speeds. It also includes a USB-C PD input port for charging up to 100W and dual SD and TF card slots, all in a compact design.
- Flawless 4K@60Hz Video with HDMI: Delivers exceptional clarity and smoothness with its 4K@60Hz HDMI port, making it ideal for high-definition presentations and entertainment. (Note: Only the HDMI port supports video projection; the USB-C port is for data transfer only.)
- Double Up on Efficiency: The two USB-A 3.0 ports and a USB-C port support a fast 5Gbps data rate, significantly boosting your transfer speeds and improving productivity.
- Fast and Reliable 85W Charging: Offers high-capacity, speedy charging for laptops up to 85W, so you spend less time tethered to an outlet and more time being productive.
- What You Get: Anker USB-C Hub (7-in-1), welcome guide, 18-month warranty, and our friendly customer service.
Use variables with reusable workflows
A reusable workflow uses configuration variables from the caller’s repository; the repository hosting the called workflow does not automatically supply its own variables to the caller. Put reusable settings in a scope accessible to the caller, or pass workflow inputs when the called workflow should receive an explicit value. See GitHub’s reusable workflow configuration documentation.
Variable naming and documented limits
GitHub’s variable reference sets these naming rules and limits. The documentation does not state a publication year for these figures, so check the current reference before relying on them in a design with tight capacity needs.
Rank #4
- Dual Converters, Infinite Potential：Includes 2× USB C male to USB A female adapters and 2× USB A male to USB C female adapters. Perfect for a wide range of uses—tablets with Bluetooth keyboards, expand USB ports on macbook, and more. Two different converters for all your daily needs
- Next-Level 10Gbps & 3A Charging: No more slow 480Mbps, this usb to usb c adapter has a transfer speed of up to 10Gbps, allowing you to do more transferring in less time. This usb adapter fits both USB A and USB C charger, supporting up to 3A fast charging
- Upgraded Exquisite Craftsmanship: With an aluminum alloy housing and metal connector, the usbc to usb adapter is extremely durable and sturdy. Rigorously tested to withstand more than 10,000 times of plugging and unplugging, ensuring long-lasting performance
- Broad Compatible: The usb c to usb adapter widely supports all USB C/ USB A devices like laptops, tablets, cellphones, car chargers, and phone chargers. Such as compatible with MacBook Pro/Air 2023/2022, Thunderbolt 4/3 Devices,Apple MagSafe Watch 9/8/7/SE/Ultra, iPad Pro 2022/2021, Samsung Galaxy S23/S20/S10, and iPhone 17/16/15 Pro. Plug and play
- Please Note: To reach 10Gbps speed, keep the cable under 3.3 ft. For USB A Male to USB C adapters, try flipping the USB C connector. USB C Male to USB A adapters support bidirectional 10Gbps transfer within 3.3 ft
- Names may contain letters, numbers, and underscores, but cannot begin with a number or the
GITHUB_prefix. Names are case-insensitive when referenced and must be unique within their repository, organization, or enterprise scope. - Each variable’s value is limited to 48 KB.
- The documented maximum counts are 1,000 organization variables, 500 repository variables, and 100 environment variables.
- Organization and repository variables together have a 256 KB size limit per workflow run. Environment-level variables do not count toward that combined limit.
- If organization and repository variable limits are exceeded, GitHub constrains which variables are available according to documented alphabetical ordering rules.
Practical selection checklist
- Decide whether the value is sensitive. If it is, store it as a secret rather than a configuration variable.
- Choose workflow
envfor a value declared in the workflow file; choose a configuration variable when it should be managed and reused from an organization, repository, or environment scope. - Use
${{ vars.NAME }}or${{ env.NAME }}in expression contexts, and shell-specific syntax inside runner scripts. - Confirm the selected context is available at the exact workflow syntax location, especially for early expressions and environment-scoped variables.
- For reusable workflows, define the setting where the caller can access it or pass it as an input.
GitHub’s guides to storing information in variables and to variable behavior and limits provide the corresponding setup and reference details.
Quick Recap
Best Value
- 5-in-1 Connectivity: Equipped with a 4K HDMI port, a 5 Gbps USB-C data port, two 5 Gbps USB-A ports, and a USB C 100W PD-IN port. Note: The USB C 100W PD-IN port supports only charging and does not support data transfer devices such as headphones or speakers.
- Powerful Pass-Through Charging: Supports up to 85W pass-through charging so you can power up your laptop while you use the hub. Note: Pass-through charging requires a charger (not included). Note: To achieve full power for iPad, we recommend using a 45W wall charger.
- Transfer Files in Seconds: Move files to and from your laptop at speeds of up to 5 Gbps via the USB-C and USB-A data ports. Note: The USB C 5Gbps Data port does not support video output.
- HD Display: Connect to the HDMI port to stream or mirror content to an external monitor in resolutions of up to 4K@30Hz. Note: The USB-C ports do not support video output.
- What You Get: Anker 332 USB-C Hub (5-in-1), welcome guide, our worry-free 18-month warranty, and friendly customer service.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
