Tapani Moilanen

Our company is also currently pondering what to do with our Kafka library usage, basically whether there is a fork the community will back or to migrate to the new...

You could use multiple aliases in you shell configuration: ``` alias connect-cli-dev="path/to/cli -e kafka-connect.dev.example.com" alias connect-cli-prod="path/to/cli -e kafka-connect.prod.example.com" ``` Or do you mean issuing one request to multiple backends?

Hey, I had to come back to this in order to complete multi-domain support in our system. Not sure what the @knoxcard example is really about, I don't see multiple...

https://github.com/sindresorhus/xo/blob/6ec33e9776bb0da6b79529969c1c32aa098f0efc/options-manager.js#L122-L136 v0.16 Just got this. If you try to use a plugin, it results in the options array passed to eslint having a null in the extends array (because `resolve-from`...

Hi dropping in from the `@conventional-changelog` team. We have many tools for parsing git commits, doing releases etc. with different formats. I personally am most familiar with the angular convention,...

@aesopwolf The angular convention dictates that breaking change commits should have a footer of `BREAKING CHANGE:` and the rest of the commit message is reserved for that change. See [the...

@hbetts I happened to stumble across here, and yes, there are use cases for having different remotes and `package.json` `repository` fields. One of them is having a private fork (in...

Yeah @hbetts I meant git remotes in general. I don't think this is easily solvable, I don't really see `git remote origin` being much better than the package.json repo field...

@sindresorhus the linked issue is now closed, could this be implemented now?

`standard-version` is deprecated. See the deprecation notice at the start of the [README](https://github.com/conventional-changelog/standard-version?tab=readme-ov-file#standard-version) for more information or https://github.com/absolute-version/commit-and-tag-version directly for a maintained fork.