forgecode 2.11.5 (new formula)

[gliptak]

---

• 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>?
• Is your test running fine brew test <formula>?
• 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>?

---

• AI was used to generate or assist with generating this PR. Please specify below how you used AI to help you, and what steps you have taken to manually verify the changes.

---

[botantony]

There's no need to specify livecheck block unless the default strategy doesn't work as expected

[gliptak]

is there a way to validate if default strategy works? am I to remove this livecheck?

[botantony]

You can check it by running brew livecheck forgecode. In this specific case it should be fine to just remove the block

[chenrui333]

or brew livecheck --autobump forgecode

[gliptak]

updating

[botantony]

Suggested change

	assert_match "Version:", shell_output("#{bin}/forge banner 2>&1")
	assert_match version.to_s, shell_output("#{bin}/forge banner 2>&1")

Homebrew requires a simple test that checks if a program can do basic stuff correctly. From Formula Cookbook:

We want tests that don’t require any user input and test the basic functionality of the application. For example foo build-foo input.foo is a good test and (despite their widespread use) foo --version and foo --help are bad tests. However, a bad test is better than no test at all.

If software requires credentials (f.e. LLM provider API key):

If the software cannot function without credentials or requires a virtual machine, docker instance, etc. to run, a test could be to try to connect with invalid credentials (or without credentials) and confirm that it fails as expected. This is preferred over mocking a dependency.

[gliptak]

During first run, forge shows an AI selection TUI. I'm not sure how to check against it

[botantony]

Maybe it's possible to select LLM model by providing cli-args/via environment variables? Also you can try to use Open3.popen3 to write/read from stdin and stdout. If nether of these is possible, please add a comment (something like # forgecode is a TUI application)

[gliptak]

updating

[gliptak]

now it Commit style error without specifics. I can squash it locally maybe