-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Start Work operation in Home view #3621
Comments
Closed
sergeibbb
added a commit
that referenced
this issue
Oct 21, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 21, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 22, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 22, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 22, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 22, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 23, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 23, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 24, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 24, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 24, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 24, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 24, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 24, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 24, 2024
This comment has been minimized.
This comment has been minimized.
sergeibbb
added a commit
that referenced
this issue
Oct 24, 2024
This comment has been minimized.
This comment has been minimized.
sergeibbb
added a commit
that referenced
this issue
Oct 24, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 24, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 24, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 24, 2024
sergeibbb
added a commit
that referenced
this issue
Oct 24, 2024
sergeibbb
added a commit
that referenced
this issue
Nov 12, 2024
sergeibbb
added a commit
that referenced
this issue
Nov 12, 2024
sergeibbb
pushed a commit
that referenced
this issue
Nov 12, 2024
sergeibbb
pushed a commit
that referenced
this issue
Nov 12, 2024
sergeibbb
pushed a commit
that referenced
this issue
Nov 13, 2024
sergeibbb
pushed a commit
that referenced
this issue
Nov 13, 2024
7 tasks
This was referenced Nov 13, 2024
axosoft-ramint
pushed a commit
that referenced
this issue
Nov 13, 2024
(#3621, #3739) Co-authored-by: Chivorotkiv <[email protected]>
nzaytsev
added
needs-verification
Request for verification
verified ✔
Verified
and removed
needs-verification
Request for verification
verified ✔
Verified
labels
Nov 14, 2024
sergeibbb
pushed a commit
that referenced
this issue
Nov 14, 2024
sergeibbb
pushed a commit
that referenced
this issue
Nov 14, 2024
axosoft-ramint
pushed a commit
that referenced
this issue
Nov 14, 2024
#3750) (#3621, #3750) Co-authored-by: Chivorotkiv <[email protected]>
axosoft-ramint
added
verified ✔
Verified
and removed
needs-verification
Request for verification
labels
Nov 14, 2024
Verified in pre-release. |
This was referenced Nov 18, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Figma Flow Diagram
Add a "Start work" button to the Home view that opens a quick pick to initiate different flows for starting work (creating a branch).
Users should be able to create a branch, create a branch on a worktree (pro), and do either of those from an issue on a connected service (e.g, create a branch from a Jira issue).
New branches associated with issues will follow whatever naming conventions the service (e.g, Jira) requires to associate them.
Roadmap
✅ collect GitHub issues
✅ if we don't have an issue integration, suggest user to connect it. (can we have many issue providers? I believe, yes).
✅ build compatible branch name based on issue title and id
✅ Remove "read more about start work" section from "connect integrations" step:
✅ when user selects a GitHub issue, highlight the corresponding repository on the "select repo" step
❌
feature gate:✅ let user create a branch without selecting an issue (just send them to "create-branch" flow)
✅ Jira issues
❌ (not valid anymore because that step has been removed, correct?) Once you select an issue, in the next step, the description line at the top sometimes doesn't look great because it renders much of the HTML stuff as plain text. However, the HTML is rendered very well on hover, which we would like to preserve. Eric suggested, to keep both, that we put a generic line like "Created by x days ago" at the top of the description, then pad with a blank line, then can put the rest of the description. That should give us a better-looking and consistent description line in that step but also keep the HTML for the hover tooltip.
✅ filter Jira on free account
✅ Remove "create-branch" icon
✅ Make "Start Work" button open the "Start Work" quickpick
✅ fix wording
✅ filter issues to the current repo
✅ If I don't have integrations connected, when using the command, it immediately shows the "connect integration" step. This step should only show after I choose one of the "from an issue" options in the initial step.
Follow-ups
Developer's testing
Connection Flow
Pre. steps:
Flow when user connects something:
Flow when user doesn't connect anything:
Loading issues responsiveness
Expected result:
The text was updated successfully, but these errors were encountered: