GenMarkdownTreeCustom has a way to a header (filePrepender arg), however there is not a first class way to add a footer.

I have two setups, in one the -parallel option works just fine in vscode - it generates parallel test cases as it should. In the other it doesn't do anything (not reporting errors in custom flags is a problem in the vscode go plugin, which is not the issue here).

Both were installed with go get -u github.com/cweill/gotests/... when in the $HOME directory within 15 minutes of each other.

At present we can run the load generator for a set amount of time or a certain number of requests.
I would like to a mode --reconnetRequests=1000 where fortio client will reconnect after 1000 requests.

Use case: We are testing SDS cert rotation using an https fortio client (std client).
For cert rotation to be exercised fortio should reconnect periodically to fetch the new cert.
In

I just had this thought of having a GitHub action for glab.

Do we need that? 🤮

Yeah, I think we do.
Especially for repos on GitHub that are mirrored to GitLab. Maintainers may decide to accept issues and merge requests on GitHub, and write a script that automatically creates the issues and merge requests on GitLab too.
I think there are a lot of other use cases way beyond my imagina

There are several situations where users need to be kicked offline
For example
1: Login from other clients
2: The administrator thinks the user's account is abnormal
3: The server side needs urgent maintenance
And so on

At this time, the Kick method should carry a specific description, so that the client can make different prompts for different kick types

session.go
`
// Kick kicks th

Helm chart with an optional development postgres DB included.

In #150 we created the first github actions workflow that tests and releases the helm chart. In the next step, it would be great to migrate the whole CI to Github Actions in order to be consistent.

Context

Right now the tool Killgrave is using for differents companies and users, but the documentation on the repository is very poor with a very little examples. We need to improve that point to bring closer this amazing tool to more people.

Proposed implementation

The idea will be to create a doc/ directory, with an index on the main README.md listing all the features that `K