Fix README instructions for dev installation#260
Merged
borkdude merged 2 commits intobabashka:mainfrom Apr 5, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please answer the following questions and leave the below in as part of your PR.
This PR corresponds to an issue with a clear problem statement.
I have updated the CHANGELOG.md file with a description of the addressed issue.
I have considered whether I should add more tests covering the code I've changed.
Summary
As of
bbin 0.2.5, README instructions for installingneil-devfor local development did not work. After this PR, installingneil-devfrom README instructions works.References
The README dev install problem was discussed on Clojurians Slack: https://clojurians.slack.com/archives/C02FBBU61A9/p1774347319511029?thread_ts=1774345892.626849&cid=C02FBBU61A9
The
bbinREADME had the same problem (babashka/bbin#106), which was fixed (babashka/bbin@078238f).