Two's Complement Converter
Convert between signed and unsigned, with the negation steps shown.
Generate a CI workflow with caching, a version matrix and the right permissions.
The GitHub Actions Generator writes eight workflows with the parts that are easy to leave out already in: dependency caching, a matrix with fail-fast off, explicit permissions, and OIDC provenance on the publish workflow instead of a long-lived token.
Eight workflow templates covering the jobs most repositories actually need: tests across a version matrix for five languages, publishing to npm, building and pushing a Docker image, and deploying a static site to GitHub Pages.
Each one includes the details that are easy to omit and expensive to omit. Dependency caching, because an uncached install is usually the longest step in the run. A version matrix with `fail-fast: false`, so one failing version does not cancel the others and hide a second problem. Explicit `permissions:` blocks, because the default token is broader than most workflows need. And on the publish workflow, provenance through OIDC, so npm verifies the workflow itself rather than trusting a long-lived token sitting in your repository secrets.
An uncached install is usually the longest step in the run, and turning it off is one line in the setup step.
So one failing version does not cancel the rest of the matrix and hide a second, different problem.
The default token is broader than most jobs need, and a compromised dependency inherits whatever the job was granted.
The npm workflow uses OIDC provenance, so the registry verifies the workflow itself rather than a token sitting in your repository secrets.
Tests for Node, Python, Go, PHP and Rust; npm publish; Docker build and push to GHCR; and a Pages deployment.
Tests for Node, Python, Go, PHP or Rust; publish to npm; build a Docker image; or deploy to Pages.
Push, pull request, manual dispatch or a schedule, and which branch they apply to.
One or several — several become a matrix that runs them in parallel.
Save it under .github/workflows/ and push; it runs on the next matching event.
In .github/workflows/ at the root of the repository, with a .yml extension. The filename is yours to choose; the name: field inside is what shows in the Actions tab.
It is the balance most teams settle on: patches and features arrive automatically, breaking changes do not. Pinning to a full commit SHA is stricter and is what you want if a compromised action would be a serious problem for you.
Substantially. On a typical Node project, npm ci against a warm cache is a few seconds against a minute or more cold — and it is a single cache: npm line in the setup step.
The default GITHUB_TOKEN has broader access than most jobs need, and a compromised dependency inherits whatever the job was granted. Declaring contents: read and adding only what the job genuinely uses limits the damage.
What people who use the GitHub Actions Generator think of it. Reviews come from visitors and are posted as written.
No ratings yet
Yours would be the first.
0 reviews
Newest first
No reviews yet
Be the first to rate the GitHub Actions Generator. It takes half a minute and no account.
Write the first reviewConvert between signed and unsigned, with the negation steps shown.
Compute a CRC-32 checksum in hex, decimal and signed form.
Break an emoji into its code points, modifiers and joiners.
Your browser, engine, platform, languages and what it supports.
See an IP address in binary, hex and decimal, octet by octet.
Validate an IBAN's length, country and mod-97 checksum, and generate test ones.
Work out a subnet: network, broadcast, host range and usable count.
Generate Luhn-valid test card numbers that no processor will ever charge.