Add "Copy to Clipboard" to the "Copy login command" page

[chrgraefe]

On the "Copy login command" there are serveral token to authenticate against OpenShift.

Your API token is
sha256~123456789abcdefghijklmonABCDEFGHIJKLMNOPQRS

Log in with this token
oc login --token=sha256~123456789abcdefghijklmonABCDEFGHIJKLMNOPQRS --server=https://api.server.com

Use this token directly against the API
curl -H "Authorization: Bearer sha256~123456789abcdefghijklmonABCDEFGHIJKLMNOPQRS" "https://api.server.com/apis/user.openshift.io/v1/users/ ~"

---

Every single user has to click on that, select it and copy to clipboard. There should be a "Copy to Clipboard" button near every token to make it easier to do just that.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.