What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Build a failure bundle by saving the identifiers that locate the failing run and job, downloading the relevant GitHub Actions logs, retaining machine-readable test output, and uploading the collected files as a workflow artifact. GitHub provides APIs and artifact actions for those pieces, but it does not define a standard “failure bundle” format; choose a manifest, file names, and redaction rules for your project.
What to include in a failure bundle
A compact bundle should let someone identify the exact execution, see what failed, and inspect the test results without relying on an expiring download link. One possible project-defined layout is:
- Manifest: repository, workflow and run IDs, run attempt, head SHA, job ID and name, failed step when available, collection time, and a list of included files.
- Logs: the relevant job’s plain-text log, the run-attempt log archive when broader context is needed, or both.
- Test report: the structured output emitted by the test runner, alongside any human-readable summary it produces.
This is an implementation suggestion, not a GitHub-required schema. Decide file naming and redaction locally, and apply the repository’s rules for secrets and personal data before retaining or sharing files.
Choose the right log collection method
| Collection method | What it provides | Best suited to | Important limitation |
|---|---|---|---|
| Workflow-job log endpoint | A redirect to a plain-text log file for a job. | Investigating one failed job. | The download URL expires after 1 minute. Fetch it promptly. Repository read access is required; private-repository token permissions vary by token type. GitHub workflow-jobs API documentation |
| Workflow-run attempt log endpoint | A downloadable archive of logs for a particular run attempt. | Collecting broader context across a run attempt. | Its redirect URL also expires after 1 minute. An attempt’s archive may not contain every job’s logs if jobs ran in previous attempts. GitHub workflow-runs API documentation; GitHub guidance on workflow run logs |
| Workflow artifact | Files uploaded by the workflow, such as logs and structured test output, retained beyond job completion according to artifact behavior and retention settings. | Keeping results available after the job ends and sharing them with other jobs or people. | Artifacts are not a substitute for recording which run, attempt, and jobs the files represent. GitHub workflow artifacts documentation |
Collect logs through the GitHub API
Download one job’s log
- Record the repository, workflow run ID, run attempt, head SHA, job ID and name, and failed step if available. The workflow-jobs API exposes job and step information, including status details. See the endpoint documentation.
- Call GitHub’s workflow-job log download endpoint for the target job using a credential with the required repository read access. For a private repository, verify permissions for the specific token type you use.
- Follow the endpoint’s redirect and save the returned plain-text log immediately. The URL is temporary and expires after 1 minute; do not treat it as a durable reference or defer the download.
- Add the saved log to the bundle and identify its job and run attempt in the manifest.
Download logs for a run attempt
- Choose the specific run attempt whose context you need.
- Call the workflow-runs API endpoint for that attempt’s logs, then follow the redirect and save the archive immediately. Its download URL also expires after 1 minute. See the workflow-runs API documentation.
- Record the attempt number and the jobs represented by the archive. If you need complete logs for jobs across a workflow execution, check whether jobs ran in previous attempts and collect those attempts’ archives too. GitHub notes that complete logs can require archives from earlier attempts. See GitHub’s run-log guidance.
Use the job endpoint when the failure is isolated and a plain-text job log is enough. Choose the run-attempt archive when you need a broader snapshot, while explicitly marking any attempt coverage gaps.
#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.
Save test results as an artifact
Logs explain what Actions reported; a structured test report helps identify which tests failed and preserves runner-generated results in a form that other tools can process. Configure the test runner to emit a machine-readable report in a format it supports, then upload that file with the relevant logs using GitHub’s upload-artifact action. GitHub documents build and test output as artifact examples and provides download-artifact for retrieving and sharing stored files. Read the artifact documentation.
Arrange the workflow so the upload step runs after a test step fails; otherwise, a failed test may prevent the evidence from being preserved. Keep the report, logs, and manifest together when they describe the same execution, and use the artifact when you need the files to remain available after job completion.
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.
Track attempts and provenance
Retries complicate what “the run logs” means: the current attempt may not include jobs executed in an earlier attempt. A useful manifest makes that scope explicit rather than implying that a single archive is complete.
- Record the run ID and attempt number for each log archive.
- List the job IDs or names represented, including jobs retrieved separately through the job-log endpoint.
- Include the head SHA and the failed step when available, so the failure can be associated with the workflow revision and step.
- Note when the files were collected and identify which expected attempts or jobs are absent.
These fields are a practical provenance proposal based on the identifiers exposed by the APIs, not a prescribed GitHub manifest.
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.
Protect the bundle before sharing it
Logs and test reports can contain sensitive values or personal data. Apply your repository’s secret-handling and data-retention rules before uploading or distributing a bundle. Redact sensitive content in the saved files where required, and ensure the manifest describes the collected files without copying secrets into metadata.
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.
