Skip to content

Conversation

@waldyrious
Copy link
Member

Checklist

  • The page(s) are in the correct platform directories: common, linux, osx, windows, sunos, android, etc.
  • The page description(s) have links to documentation or a homepage.
  • The page(s) follow the content guidelines.
  • The page(s) follow the style guide.
  • The PR contains at most 5 new pages.
  • The PR is authored by me, or has been human-reviewed if it was created with AI or machine translation software.
  • The PR title conforms to the recommended templates.
  • Version of the command being documented (if known):

@github-actions github-actions bot added page edit Changes to an existing page(s). review needed Prioritized PRs marked for reviews from maintainers. labels Nov 1, 2025
@kbdharun kbdharun added the hacktoberfest-accepted PRs that were opened for Hacktoberfest, but may not actually get merged until November. label Nov 1, 2025
@sebastiaanspeck sebastiaanspeck changed the title git-bisect: Expand page git-bisect: expand page Nov 4, 2025
Co-authored-by: Lena Pastwa <[email protected]>
Co-authored-by: Managor <[email protected]>
@Managor Managor merged commit 306e633 into main Nov 12, 2025
9 checks passed
@Managor Managor deleted the expand-git-bisect branch November 12, 2025 13:45
@waldyrious
Copy link
Member Author

Thanks all for your suggestions and patience. As I failed to react timely and missed the merge window, I have submitted a small follow-up PR (#19361) which I hope is in line with what was being discussed here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hacktoberfest-accepted PRs that were opened for Hacktoberfest, but may not actually get merged until November. page edit Changes to an existing page(s). review needed Prioritized PRs marked for reviews from maintainers.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants