Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove deprecated sendFeedback server method #12911

Closed
wants to merge 2 commits into from

Conversation

jankeromnes
Copy link
Contributor

Description

Remove deprecated sendFeedback server method.

Note: This is completely unrelated to the new dashboard feedback mechanism. 💡

In the early days of Gitpod (I think when it was still in Beta, or fresh out of Beta) there was a simple mechanism to provide general feedback about Gitpod, and in exchange you would receive a credit of 50 bonus Gitpod hours.

This feature no longer exists, and we no longer even keep track of the provided feedback (it's logged at info level in server, which we currently discard), but the server method is still there in our API, potentially allowing clever users to credit themselves 50 hours whenever they want.

This PR removes the old, deprecated sendFeedback method. Also, removing it now is a good idea, because we have a new dashboard feedback mechanism in place, and it's too easy to accidentally mistake one for the other.

Related Issue(s)

Fixes #

How to test

  1. Build should pass
  2. Gitpod should still work

Release Notes

NONE

Documentation

Werft options:

  • /werft with-preview

@jankeromnes
Copy link
Contributor Author

jankeromnes commented Sep 13, 2022

/werft run with-clean-slate-deployment

👍 started the job as gitpod-build-jx-rm-old-feedback.2
(with .werft/ from main)

@jankeromnes
Copy link
Contributor Author

Werft was having too much trouble with this -- moving on to #12918.

@jankeromnes jankeromnes deleted the jx/rm-old-feedback branch September 13, 2022 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants