Skip to content

Commit

Permalink
Use --quiet when invoking brew
Browse files Browse the repository at this point in the history
When `brew` is used by this action, it generates a bunch of warnings
which are picked up by the github actions capture system and shown for
end users. They are noisy and most of them are expected. It's better to
suppress them and do not alert users.
  • Loading branch information
ikalnytskyi committed Oct 23, 2024
1 parent 7a757a6 commit b3c89c2
Showing 1 changed file with 6 additions and 4 deletions.
10 changes: 6 additions & 4 deletions action.yml
Original file line number Diff line number Diff line change
Expand Up @@ -82,15 +82,17 @@ runs:
echo "PQ_LIB_DIR=$PG_LIBDIR" >> $GITHUB_ENV
elif [ "$RUNNER_OS" == "macOS" ]; then
export HOMEBREW_NO_ENV_HINTS=1
export HOMEBREW_NO_INSTALLED_DEPENDENTS_CHECK=1
export HOMEBREW_NO_INSTALL_CLEANUP=1
export HOMEBREW_NO_INSTALL_UPGRADE=1
brew install --skip-post-install postgresql@${{ inputs.postgres-version }}
brew install --quiet --skip-post-install postgresql@${{ inputs.postgres-version }}
# Link PostgreSQL binaries from /usr/local/bin in order to make them
# available globally. The overwrite option is required since some
# GitHub runners come with preinstalled PostgreSQL binaries.
brew link --overwrite postgresql@${{ inputs.postgres-version }}
# available globally. Since some GitHub runners come with
# preinstalled PostgreSQL binaries, we have to unlink them first.
brew unlink --quiet postgresql@${{ inputs.postgres-version }}
brew link --quiet postgresql@${{ inputs.postgres-version }}
fi
shell: bash

Expand Down

0 comments on commit b3c89c2

Please sign in to comment.