Ruben Bartelink

@stmax82 FYI 6.1.2 is on nuget

@jcmrva the chances are #192 will ship the fix (AFAICT it is the first nuget release that includes #127)

@jcmrva FYI 6.1.2 is on nuget

As you can see I turned on requirements for comments to be resolved prior to merge I also discovered the Linear history option - which would rule out merge commits...

@nojaf looks like it worked per https://nuget.info/packages/Argu/6.1.3

@kleidemos Would you be able to provide a PR? Eirik is no longer maintaining this as of #191 Realistically the fact that this API is not a mainstream thing means...

There's a good release pipeline [and active maintainers](#191) if you (or anyone) wanted to take a run at it now...

Atm `IsUsageRequested` seems do exactly what it purports to - convey whether the `--help` option (or configured custom equivalents) has been explicitly specified. I'm not averse to an alteration/clarification to...

I ended up with a mix of ParseResults.Catch / Raise / [GetResult](#187) in Equinox and Propulsion https://github.com/jet/propulsion/blob/8349a25fd9abda31922210f710c716fcf190305c/tools/Propulsion.Tool/Args.fs#L33 https://github.com/jet/propulsion/blob/8349a25fd9abda31922210f710c716fcf190305c/tools/Propulsion.Tool/Infrastructure.fs#L13-L16 https://github.com/jet/propulsion/blob/8349a25fd9abda31922210f710c716fcf190305c/tools/Propulsion.Tool/Program.fs#L404 Ultimately if #143 had a complete answer, I would probably not...

There are [active maintainers now](#191), and an easy release mechanism, so getting an impl out the door would not be a problem now... Main constraint/assumption would be that the impl...