Ronnie

This is still on hold until huh is updated, no eta or anything.

hmm, changie definitely does validate the kind is valid, if you are using `changie new`. ``` ▶ changie new -k "Added a whoopsie" Error: invalid kind: Added a whoopsie Usage:...

> Hmm ok I'll keep that in mind. I didn't realise this was the case, that's a bit unfortunate; developers on my team have started using code review to suggest...

hmm, I got the error now, will definitely want to fix this, but it could also be fixed by general fragment validation since its basically just unable to find the...

Example error from #711 ``` Error: kind not found but configuration expects one: 'fixed-typo-checking-ci' Usage: changie batch version|major|minor|patch|auto [flags] kind not found but configuration expects one: 'fixed-typo-checking-ci' Flags: -d, --dry-run...

Hmm good point, not sure why components aren't per project. I think this type of behavior is a good reason to push more for the v2 config I was working...

> I would still keep components global but introduce the ability for them to be associated with one or more projects. > > This way a component can appear in...

> Yeap both of those would be logical extensions to being able customise the experience based on the project. Do you by chance have a public repo that you are...

> So one of the more complex repo's is [open-telemetry/opentelemetry-collector-contrib](https://github.com/open-telemetry/opentelemetry-collector-contrib). that repo has many components and a component can be used in 1 or more projects. > > With the...

https://github.com/dbt-labs/dbt-core/blob/main/.changie.yaml This is how dbt does it.