-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Add workspacecontexturl to gpcli #16096
Add workspacecontexturl to gpcli #16096
Conversation
annotations in the pull request changed, but user is not allowed to start a job |
started the job as gitpod-build-add-workspacecontexturl-to-gpicli.0 because the annotations in the pull request description changed |
/werft run 👍 started the job as gitpod-build-add-workspacecontexturl-to-gpicli-fork.0 @Kwok-he-Chu it would be great if you squash to one commit @gtsiolis do we need CLA here? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for contributing, @Kwok-he-Chu! 🍊
You'll also need to sign a CLA[1] once before merging your first contribution. Cc @meysholdt
Thanks for the ping, @akosyakov! 🏓
Build fails, the code is not formatted properly. Could you take about it please? 🙏 |
@akosyakov I've synced my fork/upmerged with main and did auto-formatting on the file, could you rerun the job? Edit: Looking at the formatting changes, it feels like I'm using a different linter that is off to your standards. Could you have a look? |
/werft run 👍 started the job as gitpod-build-add-workspacecontexturl-to-gpicli-fork.1 Could you also squash commits into one please? 🙏 |
Job seems to fail again, let's fix that first. And I'll squash everything into one commit after. "please gofmt your code" --> Could you have a look? @akosyakov |
fcae841
to
8f41461
Compare
Squashed, reformatted again, should be good now 👍 |
/werft run 👍 started the job as gitpod-build-add-workspacecontexturl-to-gpicli-fork.2 |
Looks good, what are the next steps? |
@Kwok-he-Chu Have you singed the CLA mentioned above? |
@gtsiolis Signed yes |
/werft run 👍 started the job as gitpod-build-add-workspacecontexturl-to-gpicli-fork.3 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thank you it works ❤️
/werft run 👍 started the job as gitpod-build-add-workspacecontexturl-to-gpicli-fork.4 |
Removing hold as the CLA has been signed and uploaded to the CLA folder. Thanks everyone for your patience! 🌮 🌮 🌮 🌮 /unhold |
Thanks @Kwok-he-Chu for the contribution ! 🙏 😍 ✨ |
Description
Added workspaceContextUrl to gp-cli.
I've appended the workspaceContextUrl response from the supervisor API to the
gp info
command. See #14923Related Issue(s)
Fixes #14923
How to test
cd components/gitpod-cli
go run . 'info'
Release Notes
Documentation
The documentation can be found here. From what I see, we do not need to update it. However it would be nice to complete the list. I can forward a documentation request if needed to append the following 5 (+1) variables to the list:
// This is the one I added
+1If you think it's a good idea, I'll create a docs issue.
Build Options:
Experimental feature to run the build with GitHub Actions (and not in Werft).
leeway-target=components:all
Run Leeway with
--dont-test
Preview Environment Options:
If enabled this will build
install/preview
If enabled this will create the environment on GCE infra
Valid options are
all
,workspace
,webapp
,ide
,jetbrains
,vscode
,ssh