I want to give the new shard overrides a shot, but I’m not really clear on how to utilize it in this context.
I’m working on some updates for LuckyCLI, but where it gets tricky is, this shard will generate a new Lucky app structure by creating the shards.yml file and all that. In this generated shards.yml file it normally points to a specific lucky version as a dependency. I need to point this to the master branch so I can see if recent changes will work. Running
shards install fails because
Unable to satisfy the following requirements: - `lucky (branch master)` required by `shard.yml` - `lucky (~> 0.23.0)` required by `authentic 0.6.1` Failed to resolve dependencies
I see I can create a
shard.override.yml to put some data in there, but would I add this file to the generated lucky apps? Then every time someone generated a new lucky app, they’d have this file. Or is there a better place I could put this like a global override or something? Once I have that file, what do I write exactly to tell authentic to use lucky master branch? Or do I just put lucky master in my override and then skip the need to update the shards.yml file directly? This is where I’m a little foggy on how this works…