Free tools Windows power users keep installed
One-click scans. No signup required.
To reduce repeated CI and delivery work across small repositories, first identify which steps genuinely recur, then share them at the right level: use a custom action for a reusable workflow step, or a reusable workflow for shared job or workflow logic. Set a deliberate version-reference policy so updates stay manageable without giving up control over which code runs.
The available documentation does not identify an EasyAction repository or product, so this guide covers general GitHub Actions patterns rather than attributing features or syntax to EasyAction.
As an Amazon Associate I earn from qualifying purchases.
Find the duplication worth removing
Start with a short inventory of the workflows in the repositories you maintain. Compare steps such as language and runtime setup, linting, tests, packaging, releases, and deployment. Share behavior only when it is both repeated and stable; superficially similar tasks may have repository-specific assumptions that make a shared component harder to maintain than the duplication.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsKeep repository-specific configuration at the caller boundary where practical. A shared component should make its required inputs, outputs, secrets, and environment variables explicit, rather than relying on undocumented assumptions about each repository. GitHub recommends documenting these details and an example in an action’s README. GitHub’s custom actions guidance describes that documentation practice.
#1 Best Overall
Choose an action or a reusable workflow
Use the smallest shared unit that fits the repeated task. GitHub Docs calls actions “the building blocks that power your workflow” and describes them as reusable, pre-written, configurable components. GitHub’s guidance on reusing workflows distinguishes the step-level role of actions from reusable workflows, which let callers reuse larger workflow logic.
| Choose | Best fit | How callers use it | Where it lives |
|---|---|---|---|
| Custom action | A discrete operation that fits into a workflow step, such as a standardized setup or packaging task. | As a step in a caller workflow. | For an action intended for other repositories or users, GitHub recommends a dedicated repository. For an application-specific action, it recommends keeping it in the application repository; .github/actions is one example location. GitHub’s custom actions guidance. |
| Reusable workflow | A shared job or larger workflow structure that callers should use consistently. | At the job level, rather than as an individual step. | A workflow file under .github/workflows that declares workflow_call. GitHub’s reusable workflow guidance. |
Decide whether a shared action needs its own repository
A dedicated repository can make a multi-repository or externally used action easier to discover and lets its code and releases evolve independently. GitHub recommends this arrangement when developing a custom action for other people. If the operation is private and specific to one application, keeping it inside that application repository avoids the distribution overhead of a separate project. GitHub documents both storage approaches.
Make the choice against how the component will be owned and changed: who reviews it, how often it needs releases, how callers configure it, how changes are coordinated, and which security policies apply. A shared component is not automatically simpler if every caller needs exceptions or if its release process becomes a bottleneck.
Set a reference policy before adopting shared code
How a workflow refers to a shared component determines how updates reach callers and how precisely a run is pinned. GitHub explains that a full commit SHA is unique and immutable, while tags and branches are easier to follow but can be moved. It recommends release management and major-version references for breaking changes. GitHub’s security hardening guidance covers reference choices and their integrity trade-offs.
- Full commit SHA: pins the exact revision, reducing the chance that a reference changes unexpectedly. Updating callers requires intentionally changing the SHA.
- Release or major-version tag: offers a managed update path that is easier for callers to follow, but tags can be moved. Maintain releases carefully and use major versions to signal breaking changes.
- Branch reference: is convenient when following ongoing development, but can move as the branch changes; use it only when that update behavior is intended.
Choose based on your compatibility and integrity requirements rather than applying one reference style everywhere. In particular, decide how updates are reviewed and propagated before several repositories depend on the same component.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use the same-repository reference when it fits
For repositories on github.com, GitHub announced the newer $/ syntax on July 30, 2026. It lets a workflow reference an action or reusable workflow in the same repository at the exact commit currently running, without requiring checkout for that reference. GitHub states that this syntax requires Actions runner 2.336.0 or newer. Read the GitHub changelog announcement.
Consider this option when the shared component and caller belong to the same repository and the runner requirement is met. Check compatibility before applying this guidance to GitHub Enterprise Server; the cited announcement describes github.com, not a universal availability guarantee.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteQuick Recap
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.
