Eric Satterwhite

Yes, this would need to be handled during parsing. I think its more a problem with being able to determine where a footer is ```txl \n \n \n \n \n...

Another issue with this is, if the body of the message happens to have something that matches an issue prefix, It considers everything from that point as the footer. With...

Most package managers I've encountered that handle this have allowed me to specify a url to the source. In the case of a git repo, it is just the git...

@endzyme https://github.com/luarocks/luarocks/tree/master/src/luarocks/fetch

We want to set up our own krew pugin index in our GitHub org, which is private and pulls artifacts off of private GitHub releases. Very similar to what krew...

Has there been any forward progress on this? I know there were a couple pull requests, but they seem to have stalled. Are we will waiting on agreement around design?

One thing I'm noticing missing from the `_search` api is the ability to [search across multiple indicies](https://www.elastic.co/guide/en/elasticsearch/reference/7.17/search-multiple-indices.html) ```json5 // curl -XPOST http://localhost:7200/api/v1/_elastic/ac*/_search -d '{"query": { "match_all": {} }, "size": 1}'...

The Validation for index names is a little different than what elasticsearch allows. `^[a-zA-Z][a-zA-Z0-9-_]{2,254}$` doesn't allow for a dot (period) `.` Which is allowed and common in elastic index names.

It looks like the `_bulk` endpoint is lacking the ability to create missing indexes as well

It looks like the `/` endpoint will need to support the http method `HEAD`. As far as I can tell, most elasticsearch client do this when trying to establish a...