Need help improving my GitHub Actions CI workflow

[PixelWindTech]

🏷️ Discussion Type

Bug

💬 Feature/Topic Area

Actions Runner

Discussion Details

Hi everyone,

I'm currently using GitHub Actions for my project, and I'd like to improve my workflow.

Here are a few questions I have:

1. What are the best practices for structuring GitHub Actions workflows?
2. How can I make builds faster using caching?
3. Should I split jobs into multiple workflows or keep everything in one workflow?
4. What are common mistakes to avoid when writing GitHub Actions?
5. Are there any recommended actions or reusable workflows for Node.js/React projects?

If anyone has examples of well-structured workflows or tips from real projects, I'd really appreciate it.

Thanks in advance!

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[KrrishSR4]

For Node.js/React projects, these practices have worked well for me:

1. Keep CI focused

A common structure is:

• Lint
• Test
• Build

This makes failures easier to identify and debug.

2. Use dependency caching

With actions/setup-node, you can enable package manager caching:

- uses: actions/setup-node@v4
  with:
    node-version: 22
    cache: npm

This can significantly reduce install times.

3. Split jobs when they are independent

For example:

• lint
• test
• build

can run in parallel, which reduces total workflow time.

4. Pin action versions

Prefer:

actions/checkout@v4
actions/setup-node@v4

instead of older versions to get security and performance improvements.

5. Add concurrency control

This prevents multiple runs for the same branch from wasting runner time:

concurrency:
  group: ci-${{ github.ref }}
  cancel-in-progress: true

6. Recommended actions

For most Node.js/React repositories:

• actions/checkout
• actions/setup-node
• actions/cache
• github/codeql-action (security scanning)
• actions/upload-artifact (build artifacts)

Common mistakes

• Running unnecessary builds on every event
• Not using caching
• Storing secrets in workflow files
• Keeping everything in a single large job
• Not enabling dependency or security scanning

If you can share your current workflow YAML, I can provide more specific suggestions and possible optimizations.

If this helps, please consider marking the answer as accepted so other developers can find it more easily. 🙂

[PixelWindTech]

@KrrishSR4 Thanks for this details...