-
Notifications
You must be signed in to change notification settings - Fork 281
Differentiate remote projects that are on seperate remotes #8029
Copy link
Copy link
Open
Labels
Component: ProjectsIssue needs changes to how we handle projectsIssue needs changes to how we handle projectsEffort: TrivialIssues require < 1 day of workIssues require < 1 day of workImpact: LowIssue is a papercut or has a good, supported workaroundIssue is a papercut or has a good, supported workaroundUI: ProjectsIssues with the Projects tab or related widgetsIssues with the Projects tab or related widgetsUI: Remote DialogIssues impacts the Remote DialogIssues impacts the Remote Dialog
Description
Metadata
Metadata
Assignees
Labels
Component: ProjectsIssue needs changes to how we handle projectsIssue needs changes to how we handle projectsEffort: TrivialIssues require < 1 day of workIssues require < 1 day of workImpact: LowIssue is a papercut or has a good, supported workaroundIssue is a papercut or has a good, supported workaroundUI: ProjectsIssues with the Projects tab or related widgetsIssues with the Projects tab or related widgetsUI: Remote DialogIssues impacts the Remote DialogIssues impacts the Remote Dialog
I was going through the list of recent projects and opened the "Demo Project" that contained a few demo files, low and behold that project actually was a remote one belonging to a currently inactive remote, It would be nice if in the project browser there was some indication as to which remote "owns" the project, perhaps next to the description.