Ronnie

Hmm, I wonder if wrapping these in go templates would work. The issue would still be around converting a single element on yaml to many. Not sure yet.

> What I was thinking was when determining the list of projects to process if a project contains a * it is removed from the list and in its place...

Ok more thoughts. Glob is ok, it can return multiple matches but I guess that's fine. Assuming lower case and space replacements would be too much, but you could go...

https://github.com/miniscruff/changie/discussions/610 I think the v2 format expands ( or will ) the project config to be a bit more universal.

Your alternative is currently what I'm doing haha. I think it is a fair point, would need to figure out the full spec, validate could mean many things like config...

> Agree, had not thought about, what about having seperate arguments for files/fragments and config like the update I have made above? I would say I don't think a validate...

This does bring up an idea I have considered which is to allow, for some or all of your config, to be external references. Something like file:///path or of course...

> Interesting idea, I am not that sold on remote config as it goes against reproducible builds and if someone really wanted remote files they could achieve it by downloading...

https://github.com/miniscruff/changie/discussions/610 this would be solved by my latest comment here with `ref` fields, I would like to add that as part of the v2 config format which I will actually...