Replace references to master branch

[n0toose]

• I left out one instance of master under CHANGES.md.
• I manually checked the URL and adjusted one URL that was invalid either way:
  https://github.com/panos/black/blob/b59c54ad75f7f6c11c791a03b5fe84ab2b52f37c/.flake8#L4

[n0toose]

Is there something specific that I've happened to miss that broke the checks, or was it because of the tree I used?

[cooperlees]

Just seems .github/ISSUE_TEMPLATE/bug_report.md formatting just need to be fixed by prettier.

If you run pre-commit locally it'll fix it.

[n0toose]

Just seems .github/ISSUE_TEMPLATE/bug_report.md formatting just need to be fixed by prettier.

If you run pre-commit locally it'll fix it.

On it, I'll also add a CHANGE.md message and force-push. Thank you!

[ichard26]

Sorry, but there's more references to master in gallery/, an utility script. Could you please fix them? Thank you!

Also good call on the changelog entry, this next release is going to break a lot of things... and this change will probably make that breakage even worse 😆 I'm on the fence about putting this change under documentation since while these changes are in the docs, for users any CI, random scripts, etc. references to master they have don't make sense from a documentation point of view. But then again, I can't think of anything better (Black and packaging also aren't IMO good for similar reasons).

[n0toose]

Sorry, but there's more references to master in gallery/, an utility script. Could you please fix them? Thank you!

Sure thing, I was actually just very hesitant to fix them. I'll see what I can do and get back to you if there's anything wrong.

I'll note that I'm also going to change this line, which is a reference to cpython and irrelevant to black:

black/gallery/gallery.py

Line 77 in 1bedc17

version = "master"

Also good call on the changelog entry, this next release is going to break a lot of things... and this change will probably make that breakage even worse

I don't think it will, it's mostly just documentation-related changes. Unless if you're referring to the transition from the master branch to main. GitHub just redirects that sort of stuff, sometimes.

[n0toose]

Additional note: I frankly have no idea why the CI check is freaking out. The test passes on my machine, can't see any tab/space-related sort of difference.

[n0toose]

I added an additional note regarding some source code changes, but I didn't see the changes as substantial enough to move the log away from the Documentation section.

Moreover:

(black) ~ $ pre-commit run -a
black....................................................................Passed
flake8...................................................................Passed
mypy.....................................................................Passed
prettier.................................................................Passed

[ichard26]

Thank you! Congrats on your first contribution to Black.

I'll commit my suggestion myself so you don't have to spend more time on this. I'll merge once CI passes.

[ichard26]

Looks like the Black Playground breaks on this version value, I'll see I can submit a PR over there later today so this doesn't stay broken.

[ichard26]

I may or may not have forgotten about this PR... whoops!

Clicking the magical green button now.