From a1bf34e6631db6865bd04d07c99f9936da8a53ff Mon Sep 17 00:00:00 2001 From: aptalca <541623+aptalca@users.noreply.github.com> Date: Wed, 19 Apr 2023 10:37:34 -0400 Subject: [PATCH] Update PR instructions --- index.html | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/index.html b/index.html index 6362e85..2ee598d 100644 --- a/index.html +++ b/index.html @@ -237,8 +237,9 @@
  • Fork this repo, create a new branch based on the branch template.
  • Edit the Dockerfile for the mod. Dockerfile.complex is only an example and included for reference; it should be deleted when done.
  • Inspect the root folder contents. Edit, add and remove as necessary.
  • +
  • After all init scripts and services are created, run find ./ -path "./.git" -prune -o \( -name "run" -o -name "finish" -o -name "check" \) -not -perm -u=x,g=x,o=x -print -exec chmod +x {} + to fix permissions.
  • Edit the readme with pertinent info, delete the instructions.
  • -
  • Finally edit the travis.yml. Customize the build branch, and the vars for BASEIMAGE and MODNAME.
  • +
  • Finally edit the .github/workflows/BuildImage.yml. Customize the vars for BASEIMAGE and MODNAME. Set the versioning logic if needed.
  • Ask the team to create a new branch named <baseimagename>-<modname> in this repo. Baseimage should be the name of the image the mod will be applied to. The new branch will be based on the template branch.
  • Submit PR against the branch created by the team.
  • Make sure that the commits in the PR are squashed.