Skip to content

Create setup.env in chip.sh if it does not exist #45

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.

Sign up for GitHub

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

Merged
florisdenhengst merged 1 commit into from
Sep 18, 2025
Merged

Create setup.env in chip.sh if it does not exist #45

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion chip.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,8 @@ rm /tmp/chiptemp

core_modules=($(docker run --rm -v "${PWD}":/workdir mikefarah/yq '.* | key + ":" + .' core-modules.yaml))

# If setup.env does not exist, create an empty setup.env
[ -f setup.env ] || touch setup.env
> setup.env
for module in ${modules[@]}; do
name=${module%%:*}
Expand Down Expand Up @@ -101,4 +103,4 @@ case $1 in
echo "Please use either 'build', 'start', 'stop', 'clean', 'config', 'list', 'auto-completion', or call without args to generate the necessary configuration without doing anything else."
echo "Add space-separated module names afterwards to perform the operation for specific modules."
;;
esac
esac