Failed to create sessions for projects whose fit remotes don't contain the `o...
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
Failed to create sessions for projects whose fit remotes don't contain the origin remote
This happens when creating a session on a project that has been added form a local folder which has GH remote, but renamed from origin to something else. The CopiloApp fails to create a session in this case completely.
Failed to create session: project bd1d8aca-b1d3-4e36-9b6d-0a2ae0049d52 has no origin remote; add an origin remote or remove and re-add the project
| Field | Value |
|---|---|
| App version | 1.1.20 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Day 1 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing session creation for projects added from a local folder when the GitHub remote is named something other than origin. Reproduce with a renamed remote and verify that the Copilot app creates the session without requiring an origin remote.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100