Skip to content

fix: The default branch should always come first in the branch selector #396

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.

Sign up for GitHub

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

Jump to bottom
Merged
charlesvien merged 1 commit into from
Jan 6, 2026
Merged

fix: The default branch should always come first in the branch selector #396

charlesvien merged 1 commit into from
Jan 6, 2026

Conversation

@charlesvien
Copy link
Contributor

@charlesvien charlesvien commented Jan 6, 2026

No description provided.

@charlesvien charlesvien changed the title The default branch should always come first in the branch selector fix: The default branch should always come first in the branch selector Jan 6, 2026
@charlesvien charlesvien marked this pull request as ready for review January 6, 2026 06:03
@charlesvien charlesvien requested a review from a team as a code owner January 6, 2026 06:03
@charlesvien charlesvien mentioned this pull request Jan 6, 2026
Merged
@charlesvien Graphite App
Copy link
Contributor Author

charlesvien commented Jan 6, 2026 •
edited
Loading

This stack of pull requests is managed by Graphite. Learn more about stacking.

@charlesvien charlesvien mentioned this pull request Jan 6, 2026
Merged
@charlesvien charlesvien force-pushed the 01-05-the_default_branch_should_always_come_first_in_the_branch_selector branch 3 times, most recently from cf7e38f to 573c8c4 Compare January 6, 2026 19:39
@charlesvien charlesvien force-pushed the 01-05-timing branch 2 times, most recently from 3985bed to 68cc0fc Compare January 6, 2026 19:57
@charlesvien charlesvien force-pushed the 01-05-the_default_branch_should_always_come_first_in_the_branch_selector branch from 573c8c4 to 5a995df Compare January 6, 2026 19:57
@charlesvien charlesvien force-pushed the 01-05-the_default_branch_should_always_come_first_in_the_branch_selector branch from 5a995df to c6d6586 Compare January 6, 2026 20:19
@charlesvien Graphite App
Copy link
Contributor Author

charlesvien commented Jan 6, 2026 •
edited
Loading

Merge activity

  • Jan 6, 8:24 PM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Jan 6, 8:38 PM UTC: Graphite rebased this pull request as part of a merge.
  • Jan 6, 8:40 PM UTC: @charlesvien merged this pull request with Graphite.

@charlesvien charlesvien changed the base branch from 01-05-timing to graphite-base/396 January 6, 2026 20:25
@charlesvien charlesvien changed the base branch from graphite-base/396 to main January 6, 2026 20:36
@charlesvien charlesvien force-pushed the 01-05-the_default_branch_should_always_come_first_in_the_branch_selector branch from c6d6586 to 98453ac Compare January 6, 2026 20:37
@charlesvien charlesvien merged commit d53c066 into main Jan 6, 2026
11 checks passed
@charlesvien charlesvien deleted the 01-05-the_default_branch_should_always_come_first_in_the_branch_selector branch January 6, 2026 20:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@joshsny joshsny joshsny approved these changes

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@charlesvien @joshsny