Skip to content

Fix #140, use first exact match (#141) #143

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

Merged
merged 1 commit into from
Jul 14, 2025
Merged

Fix #140, use first exact match (#141) #143

merged 1 commit into from
Jul 14, 2025

Conversation

benc-uk
Copy link
Owner

@benc-uk benc-uk commented Jul 14, 2025

I don't know why PR #141 didn't get merged to main
This fixes that

@benc-uk benc-uk linked an issue Jul 14, 2025 that may be closed by this pull request
@benc-uk benc-uk merged commit ff7c046 into main Jul 14, 2025
1 check passed
@Ghostbird
Copy link
Contributor

Ah, sorry about that. I made #141 through the VSCode extension Github Pull Requests. Sometimes it'll select the a base branch different from the default branch. There's probably a reason, but I haven't discovered it yet, as it happens rarely. Then I don't pay attention to it, since it normally selects the correct base branch, and I create the PR with the wrong base branch. And for the same reason on Github nobody expects the base branch of a PR to be wrong. So it gets merged into the wrong branch. I've had it a couple of times over the past few years.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Error in graph
2 participants