You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Using concurrency and dependencies in package CI #684
I would be a bit more hesitant against lint and build jobs depending on each other, they are really different things. Also, I think it can actually lead to more CI runs. If both linting and testing/building fails separately then we can fix them in one commit (or better: two commits and one push). If you have to wait for one to get fixed before finding out the other also fails you have to do two pushes, and get two CI runs.
Activity
egpbos commentedon Apr 4, 2025
I think the concurrency check is a good default!
I would be a bit more hesitant against lint and build jobs depending on each other, they are really different things. Also, I think it can actually lead to more CI runs. If both linting and testing/building fails separately then we can fix them in one commit (or better: two commits and one push). If you have to wait for one to get fixed before finding out the other also fails you have to do two pushes, and get two CI runs.