The Tool Desk
Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →To use Argos CI with a private GitHub repository, sign in to Argos with GitHub, install or authorize its GitHub integration for the repository, then configure your CI workflow to upload visual-test screenshots. The documented GitHub Actions example uses an ARGOS_TOKEN secret; Argos later announced GitHub OIDC authentication for supported runs. Check the installation screen’s requested permissions and selected repositories, because access is limited by the GitHub account’s app-installation scope.
1. Connect the private repository to Argos
- Sign in to Argos using GitHub, following the Argos Storybook and GitHub Actions setup guide.
- In the Argos dashboard, add the repository you want to test. If GitHub asks you to install or authorize the Argos app, confirm that the correct personal account or organization is selected.
- On GitHub’s installation screen, inspect the requested permissions and repository scope before confirming. If the installation is limited to selected repositories, include the target private repository. GitHub advises app owners to request only the permissions they need, and the installer controls which accessible repositories are in scope. See GitHub’s app-permission guidance and GitHub’s authorization documentation.
- Return to Argos and follow the project’s setup instructions. Use the live installation screen as the authority for the specific permissions Argos currently requests; generic GitHub documentation does not establish Argos’s exact permission list.
If your organization restricts third-party apps, an organization owner may need to approve or install the integration. If the repository does not appear in Argos, verify both the GitHub account used to authorize the app and the selected-repository scope.
2. Add visual testing to GitHub Actions
Argos’s published example is built around Storybook: it installs dependencies and browser support, builds and serves Storybook, runs visual tests, and uploads the resulting screenshots. It runs on pull requests and pushes to main. Those commands are an example, not a requirement that every project use Storybook. Adapt the build and test commands to the framework already used by your repository; use the setup instructions for the test stack you have configured.
The guide describes its example this way: “This workflow triggers on every push to main and on pull requests. It will build Storybook, serve it locally, run the tests, and upload screenshots to Argos.” See the full Argos guide for its current package and workflow details.
#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.
Keep the workflow aligned with your project
- Keep the pull-request trigger if you want visual results on proposed changes; include a push trigger for your main branch if you also want baseline updates or results on direct pushes.
- Use the same build and test commands that work locally or in your existing CI. Do not copy Storybook-specific commands into a project that does not use Storybook.
- Make the screenshots available to the Argos upload step, and ensure the upload step runs after the visual tests have produced them.
- Start with the Argos-generated setup for the selected project, then adapt workflow triggers and job permissions deliberately rather than adding broad permissions by default.
3. Choose upload authentication: token or OIDC
| Method | Setup | When to consider it |
|---|---|---|
ARGOS_TOKEN secret |
The Argos GitHub Actions guide documents storing the project token as a GitHub Actions repository secret and making it available to the workflow. | Use this documented setup when your project instructions specify a token and OIDC is not enabled for the run. |
| GitHub OIDC | Argos’s May 11, 2026 changelog says to enable OIDC in Argos project settings and grant the workflow id-token: write; for supported runs, the long-lived ARGOS_TOKEN secret can then be removed. |
Consider it for supported runs when you want short-lived GitHub-signed identity rather than a reusable token secret. Follow the current project configuration and Argos instructions. |
The OIDC setup and its limitations are described in Argos’s May 11, 2026 authentication changelog. It also describes a tokenless fallback for forked pull requests and public repositories when OIDC is unavailable, after Argos verifies repository, commit, branch, and workflow-run details through GitHub’s API. Do not assume that this covers every private-fork event, organization policy, or workflow configuration; verify your intended event path in the current Argos documentation.
Protect the secret-based workflow
- Create or copy the Argos token using the project’s Argos setup instructions.
- Add it in the repository’s GitHub Actions secrets, then reference the secret in the upload step as instructed. Do not commit a token into the workflow file or source tree.
- For repositories governed by organization policies, check whether the workflow can access repository or organization secrets for the event being run.
- If you switch a supported job to OIDC, enable it in Argos and add only the documented
id-token: writepermission needed for that authentication flow. Remove the token secret from that job when Argos’s current instructions say it is no longer required.
4. Verify the pull request result
- Open a pull request that triggers the workflow, or push to the configured branch.
- In GitHub Actions, confirm the build, visual tests, and Argos upload step complete successfully.
- Open the corresponding Argos project and check that the run is associated with the expected repository and commit.
- Review the visual-change result on the pull request. If no Argos result appears, check repository selection, workflow trigger conditions, upload authentication, and whether the upload step ran after screenshots were created.
5. Troubleshoot common setup failures
| Symptom | Likely cause | What to check |
|---|---|---|
| Private repository is missing from Argos | The app was authorized with a different GitHub account or the repository was omitted from a selected-repository installation. | Review the app installation under the correct user or organization and include the target repository in its scope, then revisit Argos. |
| GitHub blocks or delays the app installation | Organization policy may require owner approval or control third-party app access. | Ask an organization owner to review the live installation request and organization policy. Do not assume an individual repository admin can override it. |
| Upload step cannot authenticate | The configured token is missing, unavailable to that workflow event, or the job’s OIDC setup is incomplete. | For token auth, confirm the secret name and workflow reference. For OIDC, confirm the Argos project setting and id-token: write permission are present and that the run is supported. |
| Internal pull request works but fork pull request does not | Secrets and authentication behavior can differ by event and repository policy; the documented tokenless fallback is not a universal compatibility guarantee. | Check the current Argos OIDC instructions and GitHub event/security behavior for the exact fork, organization, and trigger combination. |
| Workflow passes but no visual result is attached | The workflow may not trigger on that event, the upload may run before screenshots exist, or the upload may target the wrong project. | Inspect the Actions run, step ordering, configured upload credentials, and Argos project/repository association. |
| Copied workflow fails at the build or test stage | The published example assumes a Storybook-based flow and its own package setup. | Replace example-specific scripts and dependencies with commands that match the repository’s application and visual-test framework. |
6. Check plan fit for private-repository use
Argos’s pricing page currently lists GitHub integration on its Hobby plan, with up to 5,000 screenshots, and Pro starting at $100 per month with 35,000 screenshots included and usage-based billing. These are the plan details displayed by Argos on October 3, 2026; they can change. The pricing page does not by itself establish that every private-repository configuration or feature is available on Hobby, so confirm current entitlement details for your repository before relying on a particular plan. See Argos pricing. The GitHub Marketplace listing presents plans differently, so do not combine its presentation with Argos’s own pricing figures.
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.
Or skip the browser setup
If your need is to capture a website screenshot from a script rather than run visual regression tests against your private repository, ScreenshotNeo is a separate website screenshot API and MCP server; it does not replace Argos CI’s repository-based visual testing. One GET request returns an image or PDF. For example:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo documentation for API options. ScreenshotNeo accepts cookie/consent banners before capture and removes known consent platforms, newsletter popups, and chat widgets; bot checks, blank pages, failed loads, and cache hits are not billed. Its MCP server provides screenshot and page-info tools for AI agents. The free plan includes 1,000 screenshots a month with no card; paid plans start at $5 for 3,000 screenshots. Sign up for ScreenshotNeo free.
Recommended Free Tools
Frequently Asked Questions
Can Argos CI connect to a private GitHub repository?
Yes, provided the GitHub app installation or authorization includes that repository and your account or organization permits the integration.
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.
Does the Argos GitHub Actions setup require Storybook?
No. Storybook is the basis of Argos’s published example; adapt the workflow’s build and test commands to your project’s existing stack.
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.
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
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.
