1
Set up our GitHub integration
Start by going to app.blacksmith.sh and follow the steps to grant Blacksmith the necessary permissions to execute your GitHub Action jobs on Blacksmith’s infrastructure.
Blacksmith is limited to GitHub organizations and not available for personal repositories.
2
Use our Migration Wizard to update your GitHub Actions workflow files
Don't see your organization in the Blacksmith dashboard?
Don't see your organization in the Blacksmith dashboard?
This could be because of a few reasons:
- The GitHub organization has SSO enabled, but the current session is not authenticated. Make sure you authenticate with the SSO provider within GitHub and then refresh the Blacksmith dashboard.
- The GitHub organization does not have the Blacksmith app installed. Verify that the Blacksmith app is correctly installed in the organization.
- The GitHub user is not a member of the organization. Double-check that the user is a member of the organization.
Diff Example
Workflow files may contain multiple jobs. Ensure you update all
runs-on
fields to utilize Blacksmith runners.3
Cache dependencies and build outputs to run even faster (recommended)
When you run jobs on Blacksmith, all official GitHub and popular third-party cache actions transparently interact
with our 4x faster, colocated cache, instead of GitHub’s backend. Plus, enjoy 25GB of free storage per repository each week, 2.5x what GitHub offers.To learn more about how we achieve this, checkout our dependencies cache page.
Diff Example
4
Cache Docker layers to make your Docker builds even faster (recommended)
Blacksmith lets your Docker builds in GitHub Actions reuse cached layers, rebuilding only what’s changed and speeding up your builds by up to 40x.To learn more about how we achieve this, checkout our Docker builds cache page.
Diff Example
5
Debug your CI pipeline using our observability features
We fill the gap GitHub left: quickly seeing what’s happening in your CI pipeline when something goes wrong.
6
Tell your friends