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

Investigate the ability of adding of public key to Bitbucket and GitLab #19186

Closed
2 tasks
vitaliy-guliy opened this issue Mar 2, 2021 · 1 comment
Closed
2 tasks
Assignees
Labels
area/plugins kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@vitaliy-guliy
Copy link
Contributor

Is your enhancement related to a problem? Please describe.

Given that we know how to add a public key to GitHub, it would be nice to have the same functionality for Bitbucket and for GitLab.

Screenshot from 2021-02-22 14-19-56

This is how workspace startup looks when the user is creating a workspace with two Git SSH projects, one from GitHub and another one from Bitbucket. To GitHub it's possible to add the public key by simple clicking on the button.
For Bitbucket it needs to copy public key and add it to the account by hands.

Describe the solution you'd like

Investigate the ability to add public key to

  • Bitbucket
  • GitLab
@vitaliy-guliy vitaliy-guliy added kind/enhancement A feature request - must adhere to the feature request template. area/plugins labels Mar 2, 2021
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Mar 2, 2021
@vitaliy-guliy vitaliy-guliy changed the title Investigate the ability of adding of public key to bitbucket and gitlab Investigate the ability of adding of public key to Bitbucket and GitLab Mar 2, 2021
@skabashnyuk skabashnyuk removed the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Mar 3, 2021
@ericwill ericwill mentioned this issue Mar 18, 2021
46 tasks
@ericwill ericwill added this to the 7.29 milestone Mar 24, 2021
@ericwill ericwill mentioned this issue Apr 8, 2021
42 tasks
@ericwill ericwill removed this from the 7.29 milestone Apr 14, 2021
@ericwill ericwill mentioned this issue Apr 29, 2021
32 tasks
@ericwill ericwill mentioned this issue May 20, 2021
29 tasks
@ericwill ericwill mentioned this issue Jun 10, 2021
30 tasks
@che-bot
Copy link
Contributor

che-bot commented Jan 4, 2022

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

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

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 4, 2022
@che-bot che-bot closed this as completed Jan 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/plugins kind/enhancement A feature request - must adhere to the feature request template. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

5 participants