diff options
| author | Junio C Hamano <gitster@pobox.com> | 2024-07-08 15:52:11 -0700 |
|---|---|---|
| committer | Junio C Hamano <gitster@pobox.com> | 2024-07-08 16:23:05 -0700 |
| commit | 58696bfcaacc50323e596112124b41242fde23de (patch) | |
| tree | fb0e138583cc62a00f7a5ee72710cd2c80eefbcf | |
| parent | 337b4d400023d22207bcc3c29e9ebab31bf96fc2 (diff) | |
| download | git-58696bfcaacc50323e596112124b41242fde23de.tar.gz | |
ci: unify bash calling convention
Under ci/ hierarchy, we run scripts under either "sh" (any Bourne
compatible POSIX shell would work) or specifically "bash" (as they
require features from bash, e.g., ${parameter/pattern/string}
expansion). As we have the CI environment under our control, we can
expect that /bin/sh will always be fine to run the scripts that only
require a Bourne shell, but we may not know where "bash" is
installed depending on the distro used.
So let's make sure we start these scripts with either one of these:
#!/bin/sh
#!/usr/bin/env bash
Yes, the latter has to assume that everybody installs "env" at that
path and not as /bin/env or /usr/local/bin/env, but this currently
is the best we could do.
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| -rwxr-xr-x | ci/check-directional-formatting.bash | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/ci/check-directional-formatting.bash b/ci/check-directional-formatting.bash index e6211b141a..3cbbb7030e 100755 --- a/ci/check-directional-formatting.bash +++ b/ci/check-directional-formatting.bash @@ -1,4 +1,4 @@ -#!/bin/bash +#!/usr/bin/env bash # This script verifies that the non-binary files tracked in the Git index do # not contain any Unicode directional formatting: such formatting could be used |