datree 0.7.1 (new formula)

[chenrui333]

• 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>?

---

relates to datreeio/datree#115

[chenrui333]

@dimabru, you might want to update the default branch on datree side?

datree:
  * HEAD: Use `branch: "staging"` to specify the default branch

[chenrui333]

I am gonna temporarily switch back to staging branch (as it is the listed default branch).

[romanlab]

@chenrui333 You're absolutely right, our default branch is staging.

But we use staging because we want all pull requests to go automatically to the staging branch, so we can verify the version on our staging environment before we promote it to production.

All stable, production level releases are on our main branch and therefore Homebrew should also point to the main branch to make sure it always references a stable version

[SMillerDev]

All stable, production level releases are on our main branch and therefore Homebrew should also point to the main branch to make sure it always references a stable version

That's not what the head block is for though. head allows users to do a build from a recent git checkout (to validate patches for example). For the stable version we just use the tagged downloads.

[BrewTestBot]

@SMillerDev has triggered a merge.