Directory tree and GIT access#
Standard directory structure#
Each user should place (either physically or through symbolic links)
sdt.dailyxxx .sdtcheck patchupgradesdtcheck patchmklxxx / sdtdef problem if existclone by url https://github.com/SDTools-support/support
xxx clone_Support.png
For internal SDTools processes this is
sdt.cursdt.gitcontains all the project directories. For examplesdt.git\supportshould be a clone from https://github.com/SDTools-support/support
sdt.git/reposhould then contain the standard directoriessdt.git\repo\mshould contain.msource files. Standard file names ared_*.mcorrespond to demos and are never pcoded.t_*.mcorrespond to test files.*(year).mdev24.mcorrespond to a project and the associated year.
sdt.git\repo\texshould contain.texsource files.sdt.git\repo\tex\plotscan contain.texsource files but do not add binary figures (png/pdf/jpg) in the directory.sdt.git\repo\jupshould contain.mdor.rstsource files for documentation generation.
GitHub desktop as git interface#
GitHub desktop is an intuitive interface for Git access. It is the choice used by SDTools to explain git to users that are not familiar with this versioning system.