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

I was wondering if there is a way to deal with issues in a file-like approach. For example

$ glab issue view 123 >> tmp.md
$ xdg-open tmp.md
$ glab issue update 123 --file tmp.md

That is, download the issue to a temporary file, edit as needed, update isse using the modified file.

This would be handy also to clone issues or to use an issue as a template:

$ glab issue c

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

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