tidy-viewer 1.4.6

[alexhallam]

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

[carlocab]

Not sure why the checksum doesn't match, but here's the right one.

[alexhallam]

@carlocab I made the mistake of running sha on my apple binary as opposed to the tar.gz binary. It is all good now.

[carlocab]

Thanks! For future reference, our preferred commit message style for version bumps is something like

tidy-viewer 1.4.6

Additionally, please don't push merge commits to your PR branch. These it more difficult to merge your PR because of our repo's linear history requirement. (That's where the automerge-skip label came from.)

Finally, if you have a local installation of brew handy, you can automate all this with something like

brew bump-formula-pr --version=1.4.6 tidy-viewer

Or, failing that, you can use this GitHub Action to automate the creation of version bump PRs when you cut a new release.

[alexhallam]

That works.

is the command brew bump-formula-pr --version=1.4.6 tidy-viewer run in by local homebrew forked directory or can I run it from anywhere?

[carlocab]

You can run it anywhere. Note that bump-formula-pr will automatically create a new PR branch and push it to a fork on GitHub, so it will need access to credentials (but these can be cached).

[BrewTestBot]

🤖 A scheduled task has triggered a merge.