I would like to parameterize the command name based on the parameters from the parameter list

Currently the --command-name only seem to take into account the first one in the list it would be nice if we could parametrerize the --command-name with the <VAR> as we do in the actual command

Here is a concrete example I'm running

hyperfine "brun -c opt -- //simwork/examples:Hepatitis

The original issue was reported in dotnet/performance#1701:

// Benchmark Process Environment Information:
// Runtime=.NET 6.0.0 (6.0.21.11801), X64 RyuJIT
// GC=Concurrent Workstation
// Job: Job-AQTFSE(PowerPlanMode=00000000-0000-0000-0000-000000000000, IterationTime=250.0000 ms, MaxIterationCount=20, MinIterationCount=15, WarmupCount=1)

OverheadJitting 

Is your feature request related to a problem? Please describe.

No API docs are published for the benchmark library.

Describe the solution you'd like

Publish basic Doxygen HTML docs online. This is fairly straightforward with Travis + GitHub pages, if you don't want to use a separate doc hosting site.

• I have marked all applicable categories:
  • exception-raising bug
  • RL algorithm bug
  • documentation request (i.e. "X is missing from the documentation.")
  • new feature request
• I have visited the [source website], and in particular read the [known issues]
• I have searched through the [issue tracker] and [issue categories] for duplicates
• [ ]

We keep this issue open to collect feature requests from users and hear your voice. Our monthly release plan is also available here.

You can either:

1. Suggest a new feature by leaving a comment.
2. Vote for a feature request with 👍 or be against with 👎. (Remember that developers are busy and cannot respond to all feature requests, so vote for your most favorable one!)
3. Tell us that you wo

We keep this issue open to collect feature requests from users and hear your voice. Our monthly release plan is also available here.

You can either:

1. Suggest a new feature by leaving a comment.
2. Vote for a feature request with 👍 or be against with 👎. (Remember that developers are busy and cannot respond to all feature requests, so vote for your most favorable one!)
3. Tell us that you wo