Skip to content

foxglove-cli 1.0.23 (new formula) #225105

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
1 commit merged into from
May 30, 2025
Merged

foxglove-cli 1.0.23 (new formula) #225105

1 commit merged into from
May 30, 2025

Conversation

sofuture
Copy link
Contributor

  • 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 HOMEBREW_NO_INSTALL_FROM_API=1 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 HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

This PR adds foxglove-cli, a tool for interacting with the Foxglove multimodal data observability platform.

@github-actions github-actions bot added go Go use is a significant feature of the PR or issue new formula PR adds a new formula to Homebrew/homebrew-core labels May 29, 2025
@github-actions github-actions bot added the autosquash Automatically squash pull request commits according to Homebrew style. label May 29, 2025
@github-actions github-actions bot removed the autosquash Automatically squash pull request commits according to Homebrew style. label May 29, 2025
Copy link
Contributor

Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request.

@github-actions github-actions bot added the autosquash Automatically squash pull request commits according to Homebrew style. label May 30, 2025
@github-actions github-actions bot removed the autosquash Automatically squash pull request commits according to Homebrew style. label May 30, 2025
daeho-ro
daeho-ro previously approved these changes May 30, 2025
Copy link
Contributor

⛔ It looks like @BrewTestBot cannot push to your PR branch. Please open future pull requests from a non-organization fork to simplify the merge process.

@github-actions github-actions bot added the no push access Maintainers cannot push to this pull request. label May 30, 2025
chenrui333
chenrui333 previously approved these changes May 30, 2025
Copy link
Contributor

🤖 An automated task has requested creation of a replacement PR.

@github-actions github-actions bot dismissed stale reviews from daeho-ro and chenrui333 May 30, 2025 02:34

Replacement PR dispatched

@github-actions github-actions bot added automerge-skip `brew pr-automerge` will skip this pull request superseded PR was replaced by another PR labels May 30, 2025
@BrewTestBot BrewTestBot marked this pull request as draft May 30, 2025 02:35
Copy link
Contributor

✅ Replacement PR created at #225168.

Copy link
Contributor

⚠️ Pre-merge checks failed.

@github-merge-queue github-merge-queue bot closed this pull request by merging all changes into Homebrew:master in b9ba456 May 30, 2025
@sofuture
Copy link
Contributor Author

Thanks @chenrui333 @daeho-ro 🙏

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
automerge-skip `brew pr-automerge` will skip this pull request go Go use is a significant feature of the PR or issue new formula PR adds a new formula to Homebrew/homebrew-core no push access Maintainers cannot push to this pull request. superseded PR was replaced by another PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants