Skip to content
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

Fix for foreman existence test in rbenv installs. #91

Merged
merged 1 commit into from May 2, 2022

Conversation

MrJoy
Copy link
Contributor

@MrJoy MrJoy commented May 1, 2022

Per #87:

Because rbenv uses shims, the existence of foreman in any gemset will result in this test passing (indicating that the tool is available), whether it's in the current gemset or not.

This test, courtesy of @t27duck, ensures that foreman is actually operable in the current context.

Because rbenv uses shims, the existence of foreman in any gemset will result in this test passing (indicating that the tool is available), whether it's in the current gemset or not.

This test, courtesy of @t27duck, ensures that foreman is actually operable in the current context.
@dhh dhh merged commit f264e3f into rails:main May 2, 2022
@t27duck
Copy link
Contributor

t27duck commented May 2, 2022

@MrJoy This should probably be done in jsbundling-rails too.

@MrJoy
Copy link
Contributor Author

MrJoy commented May 3, 2022

@t27duck Ah! Good call! Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants