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
On project with multiple developers we are unlikely to be able to have a single person gating changes made to taskfiles and even if we would do, it is too easy to introduce dependency errors which would make task run when they should not.
To address this one could try to modify how tasks are run on CI to cause failures if on second consecutive run they do not report up-to-date.
The issue is that the boilerplate code needed for doing this is really ugly
task build && \
task build |& tail -n 1 f || grep -v 'is up to date'>/dev/null || \
{ echo"Failed as task command did not had 'sources' and 'generates' correctly defined.";exit 55;}
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
On project with multiple developers we are unlikely to be able to have a single person gating changes made to taskfiles and even if we would do, it is too easy to introduce dependency errors which would make task run when they should not.
To address this one could try to modify how tasks are run on CI to cause failures if on second consecutive run they do not report
up-to-date.The issue is that the boilerplate code needed for doing this is really ugly
Is there a better way to implement this?
Beta Was this translation helpful? Give feedback.
All reactions