-
-
Notifications
You must be signed in to change notification settings - Fork 624
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
Global preconditions #405
Comments
Hi @duboiss, This sounds like a good idea, but I have no plans to implement that soon... |
I will check this one out to see if i can add it with the code in the repo now. @andreynering Will you accept a PR for this or would that be planned later and you can't accept a PR even if there was one? Is so then you can assign me :) |
Hi @DanyHenriquez, I'm not sure. This is not trivial to implement so it may need some thought first. Also, there are other priorities for now. |
@andreynering @duboiss So I suggest, if there will be PR for that to consider a more global preconditions like Example:
|
@andreynering Hit me up and let me know where you need help |
Cleaning up my queue. Unfollowing since i don't know the status or if help is needed. Let me know if this changes 😄 |
Looks like a duplicate of #294. |
There is a way to reuse preconditions by the use of YAML anchors:
The anchor have to be on the same YAML file. However we could reference YAML anchors in the documentation 👍 |
Since we do not use strict YAML unmarshal, even this is possible:
|
Duplicate of #294 |
I'm new with Taskfile. I start to write my first Taskfile.yaml and I realize a serious problem : preconditions.
It's a great option but from what I see we can't store a precondition so I have several duplications.
It would be nice if we can have something similar to:
So like when you reference a task to be executed in a task. Or if you have a better idea...
The text was updated successfully, but these errors were encountered: