Skip to content

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

Sign in

Sign up

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

inobulles / bob Public

Notifications You must be signed in to change notification settings
Fork 0
Star 3

Code
Issues 13
Pull requests
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Actions
Projects
Security
Insights

Sloppy `bob sh`#77

Merged

obiwac merged 7 commits intomaininobulles/bob:mainfrom bugfix/sloppy-shinobulles/bob:bugfix/sloppy-shCopy head branch name to clipboard

Nov 24, 2024

+58-6

Conversation Commits7 (7)Checks Files changed

Commits

Commits on Nov 24, 2024

readme: Completely forgot to document bob sh
obiwac
committed
readme: Actually, we need sh -c to evaluate $PATH
obiwac
committed
sh: No idea how that happened
obiwac
committed
sh: Explicit message when entering shell, because it's not always clear
obiwac
committed
tests: Tests for bob sh
obiwac
committed
sh: Don't require the setting of POSIXLY_CORRECT on Linux
obiwac
committed
run: Don't require the setting of POSIXLY_CORRECT on Linux
obiwac
committed

Footer

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Sloppy `bob sh`#77

Commits on Nov 24, 2024

readme: Completely forgot to document `bob sh`

readme: Actually, we need `sh -c` to evaluate `$PATH`

sh: No idea how that happened

sh: Explicit message when entering shell, because it's not always clear

tests: Tests for `bob sh`

sh: Don't require the setting of `POSIXLY_CORRECT` on Linux

run: Don't require the setting of `POSIXLY_CORRECT` on Linux

Commits

Commits on Nov 24, 2024

readme: Completely forgot to document bob sh

readme: Actually, we need sh -c to evaluate $PATH

sh: No idea how that happened

sh: Explicit message when entering shell, because it's not always clear

tests: Tests for bob sh

sh: Don't require the setting of POSIXLY_CORRECT on Linux

run: Don't require the setting of POSIXLY_CORRECT on Linux

readme: Completely forgot to document `bob sh`

readme: Actually, we need `sh -c` to evaluate `$PATH`

tests: Tests for `bob sh`

sh: Don't require the setting of `POSIXLY_CORRECT` on Linux

run: Don't require the setting of `POSIXLY_CORRECT` on Linux