Closed gtsiolis closed 5 months ago
It was a little awkward to have to create a team for myself just to get to setting up a prebuild for a repo (or maybe I missed how to skip that?).
It also wasn't immediately clear to me how the prebuilds would work by branch, nor is it still (though I feel like if I look in the docs that may be mentioned somewhere?) . Actually nvm I found the Branches page...
Can't say I noticed the performance difference on my first try opening a workspace, but I know a few months ago the prebuild would've probably saved me 20+ minutes after opening a workspace, so I'm super pumped to try it out more.
@Grunet use prebuild not need team
You can visit https://www.gitpod.io/docs/prebuilds for documents
It was a little awkward to have to create a team for myself just to get to setting up a prebuild for a repo ...
@Grunet you can also add repositories as a projects under your personal account. No need to create a separate team for that unless you're interested in inviting and giving access to the project for other collaborators. Cc @iQQBot
@Grunet use prebuild not need team
You can visit https://www.gitpod.io/docs/prebuilds for documents
Ahh I see. I may've been confused/too excited reading through the email I got about it, and naively followed the new onboarding workflow thinking it was the only way to get there. Thank you both for clearing that up!
I would love to see the ability to share or transfer ownership of a workspace between team members. Launching a new workspace based on the existing feature branch works well, but sometimes there are other supporting elements that have been setup that are easier to just hand off. We currently share the workspace, but it's not ideal because the non-owner cannot launch the workspace if it is stopped.
@cjensenius it sounds like you would like to share snapshots as they would actually capture a state of your workspace's artifacts, see https://www.gitpod.io/docs/sharing-and-collaboration#sharing-snapshots.
Thanks @AlexTugarev! I took a look and it seems just like what I'm looking for. I ran into an issue when I attempted to use it this morning and will file a proper bug report Looks like the issue is already solved: https://github.com/gitpod-io/gitpod/issues/5862
We run a self-hosted instance of Gitlab. I can't seem to find a way to add a project for that git instance, only gitlab.com and github.com are shown.
I really love the project dashboard :clap: so it would be great if I can add projects from our self hosted gitlab instance.
Thank you for your feedback @hjvvoorthuijsen - we are tracking this request in βοΈ #5115
I'm having some trouble getting Gitpod to recognize all the repositories it's been given access to in our organization. I shared two repos, and even created a workspace for the second one using gitpod.io/#https://github.com/foo/bar
, but it doesn't show up under https://gitpod.io/new.
Any tips?
@acrefoot I would suggest checking that you have the GitHub App for gitpod.io configured with access to your org and repositories. You can do this by visiting https://github.com/apps/gitpod-io/installations/new
This link is also shown below the list of repos at gitpod.io/new where it says Repository not found? Reconfigure
.
Not sure what's going on here. I'm trying to create a project for a repo in my org so I can view and manage prebuilds. It says "already taken", but as far as I know, no one has created a project for it.
@chuck-confluent Currently, we allow projects to be added only once across an instance. We recently shipped a change that includes the username who added a project. This indicates the repository has been added as a project under their personal account or a another team where they can invite you to join.
Mention the user who added a project |
---|
We're discussing also how we could make it easier to request to join a team when you see a project that has already been added, see https://github.com/gitpod-io/gitpod/issues/7007.
From a customer call: When someone edits the .gitpod.yml
configuration in the dashboard, there is no visual indication whether the changes were saved.
Also, if multiple team members edit the configuration, it is unclear which settings will be used - the assumption is whoever saves last.
Hi
We are connected with BitBucket and we cannot see all our repositories; if I check the network log I can see that the response contains 100 records. I wonder if we are hitting a pagination limit or similar? We currently have 130 repositories and the ones we want to add to GitPod of course are not showing.
Thanks
Hello! Getting started with gitpod and noticed that when creating Project from the bitbucket cloud repository in "Branches" available only 10 branches. Probably caused because of default bitbucket pagination
P.S. gitpod is really nice tool
Thanks in advance
Thanks for the feedback, @YesmanMaxim!
We deliberately surface only the 10 most active branches for projects until we figure out a better way how to fetch more branches efficiently with proper pagination or caching, see https://github.com/gitpod-io/gitpod/issues/5038. Let us know if you are not seeing this for the Bitbucket repository.
You can also search through other active branches that are not listed there, too.
Cc @jldec
@gtsiolis, thanks for the answer, but
Search fix will be enough for usage, right now I able to open the required branch only via the browser extension
Ah, maybe we're using different limits on the Bitbucket integration. @AlexTugarev Do you know? Cc @jldec
The listings on Branches pages is quite expensive, thus we decided to cut the queries at 10 items initially. I'm not entirely sure how helpful or maybe even misleading the search bar is on this page π€·π»
The next iterations goal was/is to introduce pagination+search as to the Project's API, so that we can make use of it on the providers side. Unfortunately, this is a bit delayed β but definitely not forgotten.
Sidebar: while implementing the provider's API requests to back this, there were several issues revealed. For instance at least one provider does not support querying branches by date of last commit at all. That means, a sophisticated caching strategy is required to allow the pagination with acceptable response time.
Noce
require("@babel/register");
De
What's the relationship between workspaces <> teams?
What's the relationship between workspaces <> teams?
You can think of teams as Github orgs where org owns the repos. Here's some relevant docs: https://www.gitpod.io/docs/teams-and-projects#title
I don't used it yet, but i think that it can be useful π
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
When trying to create a pod using a repository on my team window the following message appears:
Additional authorization is required for Gitpod to watch your GitHub repositories and trigger prebuilds.
Nevertheless clicking on Configure Gitpod App
gets me to the unicorn page of Github that states:
This page is taking too long to load. Sorry about that. Please try refreshing and contact us if the problem persists.
With my personal workspace I'm having no problem to visualise my repositories and launch pods from them
I'm running enterprise self hosted connected to SaaS Gitlab in an organization with thousands of repositories. It took about a minute to load the list of repos to choose from and it's not practical for me to find the one I need. We heavily make use of Gitlab subgroups to sort projects by org and team but the UI only displays the repo name. We have many projects with same or similar names but in different orgs so we can't distinguish between them here.
In our case it would help if we could filter by subgroup first then list the projects.
Feedback from a discord thread.
A settings icon within a project card would help. From the thought of: "where should i click to see project variables? i was missing the obvious step that clicking the project name would open it (and not open a gitpod of it)."
Not too hard to find, "but probably hard for screen readers / accessibility".
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Objective
The aim of this issue is to gather feedback on the Teams & Projects feature to be released in
AugustOctober 2021. Any feedback is welcome! See also relevant blog post[1] and changelog entry[2].Background
The upcoming Teams & Projects feature aims to :a: surface Prebuilds in the dashboard by allowing users to add repositories as Projects to their account grouped inside Teams as well as :b: introduce an onboarding flow to help users get a well-configured, prebuilt, ready-to-code dev environment for their project.
See relevant roadmap item. πΊοΈ
See also
π§βπ crew: teams and projects
label and relevant project in the issue tracker. πCc @jankeromnes @AlexTugarev @jakobhero @JohannesLandgraf @svenefftinge
Feedback
Any feedback is welcome but we're primarily looking for the following types of feedback:
Feel free to send in any comments, thoughts, emojis, screenshots, or screencasts as well as open any new separate issues with a concrete problem statement for further discussion. π¬