golang-application

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

Describe the bug
Tags are not showing for the last entry in ticker, when scrolling is applicable.

To Reproduce
Steps to reproduce the behavior:

1. launch with --show-tags
2. Scroll to the bottom
3. Observe that the last entry does not show the tags.

Expected behavior
The interface will allow you to scroll down to the very bottom.

Screenshots
![image](https://user-

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.

Right now the type for dflag.DynJSON has to be &someType and can't be directly []someType

forcing you to create an extra

type someTypeList struct {
	List []someType
}
// to pass to
myList := dflag.DynJSON(flag.CommandLine, "mylist", &someTypeList{}, "...t")

instead of directly

Describe the feature or problem you'd like to solve
My team has its issue board not on a specific repo, but on a group above the repos, currently it seems that glab doesn't allow selecting issue boards on groups, only on repos, so I can't display our issue board.

Propose a Solution
Find issue boards from all parent groups for the repo that is the currently open folder in the terminal,

In the current version, only the Handshake is used at the start of the connection. If the client does not send a message for a long time, the session will not be closed automatically. Will future versions do this session logic maintenance? For example, Netty can set the session to be automatically closed if the client does not send messages for a long time .

We should have a group support to handle permissions access from a LDAP, SSO, ...

allowed_resolvers_groups on templates for example.
admin_groups on configuration for example.

Describe the bug

Right now the deployment yaml (from the helm chart) has the same liveness and readiness probe:

          readinessProbe:
            httpGet:
              path: /config
              port: http
            initialDelaySeconds: 1
            periodSeconds: 3
          livenessProbe:
            httpGet:
              path: /config
              port: ht

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