GitHub Actions Basics: One CI Check You Can Trust
The minimal GitHub Actions CI workflow I drop into JavaScript projects: one runner, two commands, and a green check that verifies the build on every push.
Posts tagged “ci”
What is the ci tag? The ci tag collects 1 article from Bradley Matera's portfolio covering ci-related topics in web development, cloud engineering, and AI. Each article includes real project examples, code snippets, and verification steps — not generic tutorials.
1 article spanning 25.0–25.0. Written by Bradley Matera, a web developer in Durand, Illinois, serving Northwest Illinois with website design, SEO, and full-stack development. Last updated 25.02.2025.
What you'll find in these articles
These 1 article covers ci-related topics from a practical, hands-on perspective. Each piece is based on real projects, experiments, or problems I solved — not theoretical overviews. You'll find code examples, before-and-after comparisons, and specific tools or techniques that worked in practice.
Articles in this tag
The following 1 article is tagged “ci”:
| Title | Date | Read time |
|---|---|---|
| GitHub Actions Basics: One CI Check You Can Trust | 25.02.2025 | 7 min |
Key takeaways from these 1 article
- Each ci article is written from direct experience — building, debugging, or researching real projects. Source code is linked where available.
- Code examples are tested and verified before publishing. Where claims reference external documentation (e.g., Google Search guidelines, MDN), source links are included inline.
- Articles are dated and updated when tools or best practices change — check the article date for context.
- Author: Bradley Matera, a web developer in Durand, Illinois. Questions or corrections? Contact me — I respond to reader questions.
Explore related tags
Looking for more topics? Browse all tags or visit the blog index for the full archive.