Add beta label on usage

[gtsiolis]

Description

This will add a BETA label on the usage page with a link to send feedback.

We need a public feedback issue to link to. 💡

Opened this after we briefly discussed this with @laushinka in a recent social call. 🍷

How to test

Go to usage and notice the new beta notice on the left sidebar.

Release Notes

Add beta notice and label on usage

Werft options:

• /werft with-preview
• /werft with-payment

[gtsiolis]

issue(blocking): Before merging this, make sure there's a public feedback issue that we link to. 💡

[gtsiolis]

@jldec WDYT? Alternatively, we could make the label more prominent by placing it next to the tab itself, see screenshot below. I think it's worth marking this as beta, more than Teams & Projects which is far more stable, especially since this could involve charges, etc. 💸

[filiptronicek]

👀 I think like the label in the tab even more. It makes it clear this feature is in beta right from the get go - even before clicking on the section.

I am unsure though if this is worth giving up the nice Send feedback link.

[werft-gitpod-dev-com]

started the job as gitpod-build-gt-add-label-beta-on-usage.2 because the annotations in the pull request description changed
(with .werft/ from main)

[gtsiolis]

/werft run with-preview with-payment

👍 started the job as gitpod-build-gt-add-label-beta-on-usage.3
(with .werft/ from main)

[gtsiolis]

/werft run with-preview with-payment

👍 started the job as gitpod-build-gt-add-label-beta-on-usage.6
(with .werft/ from main)

[gtsiolis]

/werft run with-preview with-payment

👍 started the job as gitpod-build-gt-add-label-beta-on-usage.8
(with .werft/ from main)

[laushinka]

This looks good! For my missing context, what was the reason that it was closed before?

[gtsiolis]

@laushinka If you are referring to the closing in #12412 (comment), that was by accident while rebasing and pushing no commits to the branch. 😇

Resolved conflicts and added the missing issue link in the <a> element.

I've also replaced the Beta label with an Early Access label to be aligned with the upcoming changes in https://github.com/gitpod-io/website/pull/2715. Updated the screenshot in the PR description. Cc @jldec

[laushinka]

@laushinka If you are referring to the closing in #12412 (comment), that was by accident while rebasing and pushing no commits to the branch. 😇

Aha, got it. Btw the PR didn't create any previews. Do the labels in the description work that way? I usually always create the two tags in two lines.

[werft-gitpod-dev-com]

started the job as gitpod-build-gt-add-label-beta-on-usage.11 because the annotations in the pull request description changed
(with .werft/ from main)

[gtsiolis]

Btw the PR didn't create any previews. Do the labels in the description work that way? I usually always create the two tags in two lines.

@laushinka If you mean the Werft options in the PR description, they don't work inline. The PR was opened before I learned we need to use two lines for this to work, see relevant discussion.

Let me update the PR description and re-trigger a preview env.

/werft with-preview with-payment

👎 unknown command: with-preview
Use /werft help to list the available commands

[gtsiolis]

/werft run with-preview with-payment

👍 started the job as gitpod-build-gt-add-label-beta-on-usage.12
(with .werft/ from main)

[easyCZ]

LGTM. Adding hold in case you wanted to do any additional validation or changes.

/hold

[gtsiolis]

Thanks @laushinka and @easyCZ for taking a look, and thanks @easyCZ for adding the hold!

To unblock this, I've replaced the Early Access label with a Beta label so that the Learn more link makes sense as Early Access is a new term that does not exist yet in our docs until we merge https://github.com/gitpod-io/website/pull/2715. Once https://github.com/gitpod-io/website/pull/2715 is merged we can open a small PR to rename the label. 🛹

/unhold