Skip to content

fix(scripts): use env to find bash interpreter#3861

Merged
aldy505 merged 1 commit intogetsentry:masterfrom
Zaczero:usr-bin-env-bash
Aug 10, 2025
Merged

fix(scripts): use env to find bash interpreter#3861
aldy505 merged 1 commit intogetsentry:masterfrom
Zaczero:usr-bin-env-bash

Conversation

@Zaczero
Copy link
Contributor

@Zaczero Zaczero commented Aug 8, 2025

Updates the shebang to use #!/usr/bin/env bash for improved portability. This ensures that the script uses the bash interpreter found in the user's environment, rather than relying on a hardcoded path.

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

Updates the shebang to use `#!/usr/bin/env bash` for improved portability. This ensures that the script uses the `bash` interpreter found in the user's environment, rather than relying on a hardcoded path.
@aldy505 aldy505 requested a review from aminvakil August 9, 2025 05:31
@aldy505 aldy505 merged commit 2b549ba into getsentry:master Aug 10, 2025
9 checks passed
@Zaczero Zaczero deleted the usr-bin-env-bash branch August 10, 2025 09:17
@github-actions github-actions bot locked and limited conversation to collaborators Aug 26, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

3 participants