Skip to content

Commit

Permalink
Added a check and instrctions on how to migrate personalizations to `…
Browse files Browse the repository at this point in the history
….makerc-personal`
  • Loading branch information
AllRWeak committed Jul 1, 2024
1 parent 7af9f32 commit adf0248
Show file tree
Hide file tree
Showing 2 changed files with 21 additions and 0 deletions.
2 changes: 2 additions & 0 deletions .makerc-vars.example
Original file line number Diff line number Diff line change
Expand Up @@ -59,3 +59,5 @@ MAKEVAR_WEBHOOK_USERNAME :=Catapult
# This is the channel that will be used to send notifications to Slack or Mattermost
# Use channelname for sending notifications to a channel or @username for sending to a notifications user
MAKEVAR_WEBHOOK_CHANNEL :=

# TEMPLOOKUPFLAG
19 changes: 19 additions & 0 deletions scripts/general/checks.sh
Original file line number Diff line number Diff line change
Expand Up @@ -7,6 +7,25 @@ source ./scripts/general/colors.sh

echo -e -n "${C_CYAN}"

##########################
# .makerc-vars migration #
##########################

# Checking if .makerc-vars is already created from the example
if ! grep -q "TEMPLOOKUPFLAG" "${ROOT_DIR}/.makerc-vars"; then

echo
echo -e -n "${C_YELLOW}"
echo -e "Using ${C_MAGENTA}${ROOT_DIR}/.makerc-vars${C_YELLOW} file for personal configurations will be deprecated at 01.08.2024. Please move anything you need to ${C_CYAN}${ROOT_DIR}/personal/.makerc-personal${C_YELLOW} file."
echo -e "If you are don't know if you need to move anything, you can leave the ${C_CYAN}${ROOT_DIR}/personal/.makerc-personal${C_YELLOW} as it is. Catapult will notify you for any missing variables."
echo -e "As a last step create a new ${C_MAGENTA}${ROOT_DIR}/.makerc-vars${C_YELLOW} from ${C_BLUE}${ROOT_DIR}/.makerc-vars.example${C_YELLOW} file."

echo
read -rp "Press ENTER to continue, or Ctrl + C to cancel and make the modifications..."
echo -e "${C_RST}"

fi

######################
# Sudo command check #
######################
Expand Down

0 comments on commit adf0248

Please sign in to comment.