Skip to content
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

Configuration Change Issue #14191

Closed
ForbiddenEra opened this issue Oct 12, 2022 · 1 comment
Closed

Configuration Change Issue #14191

ForbiddenEra opened this issue Oct 12, 2022 · 1 comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@ForbiddenEra
Copy link

ForbiddenEra commented Oct 12, 2022

Edit: I'm an idiot and totally dyslexia'd a version number; thus this is not any issue but user error.

@ForbiddenEra ForbiddenEra added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Oct 12, 2022
@ForbiddenEra ForbiddenEra closed this as not planned Won't fix, can't repro, duplicate, stale Oct 12, 2022
@DHowett
Copy link
Member

DHowett commented Oct 12, 2022

Oh, thanks for following up! I'm guessing that was, "I thought 1.7 was 1.17, which would have been newer than 1.16?"

Point taken about updating the bug template, though... just to make it a little bit clearer, we should probably do that. Trust and usability is won by inches. 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Development

No branches or pull requests

2 participants