Developing the Cloverleaf site with GitHub

Cloverleaf application development in a site is an incremental process. Some files and directories come in, and some move out. The git-add, git-rm, and other git operations are a routine job over the development cycle.

Working in the local repository

Use git-checkout to check out the base site from GitHub. After this, you can continue with Cloverleaf site development, or work with other peer's changes by resolving the version conflicts upon the git-merge.

Note: gitignore needs updating if a new file and directory are appended to the root or site for SCM management.

Teamwork by GitHub "pull" request

You can git-commit and git-push the changes to the GitHub dev-developer branch after unit testing has finished.

You can also make a pull request from dev-developer to dev branch.

Peer reviews are made on NetConfig or other artifacts upon pull request, and then closed by merge.

You can trigger DevOps CI/CD to do the checking-out or exporting (git-archive) of the GitHub dev branch for the integration deployment testing.

After a release candidate version is tested and approved on the dev branch, you can do a pull request from dev to master. This closes the version development on the root/site