Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UXIT-1555 - Run linters on PRs #689

Merged
merged 5 commits into from
Oct 8, 2024
Merged

Conversation

barbaraperic
Copy link
Collaborator

📝 Description

Modify lint.yml to run on every open pull request.

  • Type: Refactor

🧪 How to Test

Can't test locally, so once it's merged, we can test with a PR coming from the CMS.

🔖 Resources

@barbaraperic barbaraperic self-assigned this Oct 2, 2024
Copy link

[FF] Run linters on PRs

Copy link

vercel bot commented Oct 2, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
filecoin-foundation-site ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 7, 2024 10:57am

Copy link
Collaborator

@mirhamasala mirhamasala left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a very broad approach, as it includes all branches, even those that may not require linting or testing, such as temporary, experimental, or draft branches. While it ensures that every pull request gets coverage, it might result in unnecessary workflow runs, potentially wasting resources and increasing build times for branches we may not care about.

What if we did something more targeted, like the example below? This would limit the workflow to main and any branches under cms/* or ecosystem-submission/*, ensuring we focus on the branches that matter most right now:

on:
  push:
    branches:
      - main
      - cms/*
      - ecosystem-submission/*
  pull_request:
    branches:
      - main
      - cms/*
      - ecosystem-submission/*

This way, we only trigger the workflow for relevant branches, avoiding excess runs while still ensuring coverage for critical parts of the project.

Copy link
Collaborator

@mirhamasala mirhamasala left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

❤️🙌🏼 Thank you!

@mirhamasala mirhamasala merged commit 26470dd into main Oct 8, 2024
5 checks passed
@mirhamasala mirhamasala deleted the bp/run-linter-on-cms-prs branch October 8, 2024 08:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants