Global .ahoy.yml

[hanoii]

It might be nice to be able to have a globally defined .ahoy.yml that can be project-wide or for personal use not to be added to the per project file.

[frankcarey]

Yes, I like this idea

[AlexSkrypnyk]

@hanoii Would $HOME/.ahoy.yml be a good place for such global file?

Also, I assume that if a per-project command exists in global config, the per-project command will take precedence, right?

[hanoii]

Yes to both! Thanks

[hanoii]

wondering if there's any renewed interest on this?

[ocean]

Hi there @hanoii - yes, it's certainly still a good idea. I'm the main maintainer for ahoy now, but haven't had a lot of time this year to spend on adding features, only the occasional security update.

I do have a couple of days off work now, so I'll have a look. One issue is we have a dependency that likely can't be upgraded without a breaking change (I think), but it's hard to tell how many people might be relying on that pattern (a cli parsing change with urfave/clilibrary).

[hanoii]

@ocean I am relying on ahoy quite a bit, and I've gotten a bit familiar with go, I am going to give adding some features a try, I wonder if you'd consider a co-maintainer for this this.

Also would you mind commenting on development processes and share more information on the above? If upgrading libraries is an issue we can always release a v3 version and do not support it, but not sure what you were taking about.