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
If not already possible, and I missed it, it would be very useful to be able to override only certain fields of a taskfile.dist.yml with a local taskfile.yml. Just like in docker compose with docker-compose.override.yml. Here is the documentation for it.
This would have several advantages: the most important, I think, are:
The taskfile.yml would usually be very short, because the fields to be overridden are usually only a few.
if any part of the dist file is modified, this is automatically inherited by the local taskfile.yml.
The text was updated successfully, but these errors were encountered:
@lrob You could use the existing include mechanism to achieve the same effect.
The specification of the included taskfile name uses a template mechanism, so it would even be possible to select which file to include at runtime. For example:
version: '3'includes:
lib:
taskfile: ./Taskfile.{{REL}}.yml //resolves to a taskfile containing task 'do_stuff'flatten: true // no namespace, just call task'do_stuff' directly
Then run task: REL=debug task do_stuff ... or similar. There is a lot of possibility from there.
If not already possible, and I missed it, it would be very useful to be able to override only certain fields of a taskfile.dist.yml with a local taskfile.yml. Just like in docker compose with docker-compose.override.yml. Here is the documentation for it.
This would have several advantages: the most important, I think, are:
The text was updated successfully, but these errors were encountered: