Having groups inside a repository will help organize the sessions related to it.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
Having groups inside a repository will help organize the sessions related to it.
Ex: If a repository has multiple applications, we cannot figure out for which application the session belogns to.
Ex: Repo1 has -> FE Project, BE Projects, BE Background Services etc.
So having groups will help to organize that is what I felt.
---
| Field | Value |
| --- | --- |
| App version | 1.0.26 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 10 |
Contributor guide
Research direction
The request concerns organizing sessions within a repository, with /chat identified as the affected path. Start by examining how repositories and sessions are currently represented in the app, then determine the grouping behavior needed for repositories containing multiple applications. Done should make sessions distinguishable and organizable by application or group.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100