I have created a github repository which is meant to include a series of python, and shell scripts. It's not your typical atomic repo because the repo actually represents all these miniprojects, one per script.
I'm trying to simplify the workflow on this repo as best as I can. But I need your help if I am actually doing it right...
The working tree is simple enough:
Therein already you can see a script, ppenv. Scripts will all be dumped into their respective shell folder. Of course some scripts may be compatible (bash and zsh tend to be, for instance). I'll be imposing a sequential rule in which scripts must be placed in order of preference: posix>bash>zsh>ksh>sh. It means that if a script is bash and zsh compatible, but not posix, it should go into the bash directory.Code:. ├── bash/ │ └── ppenv ├── docs/ │ └── ppenv ├── ksh/ ├── LICENSE ├── man/ │ └── ppenv.1 ├── posix/ ├── python/ ├── README.md ├── sh/ └── zsh/
To manage collaboration (including my own) I decided there won't be a single development branch against which collaborators do their pull requests. Instead each new script added to the repo will spawn it's own "default" branch from which collaborators may branch out and against which they can do their pull requests.
If I had 100 scripts there, this does mean a very flat git tree. But it is also one much more easy to read, since I can better trace the development of a single script.
Let me know what you think.
The thing is here:GitHub - Rahtgaz/ratscripts: Various bash and python scripts if that matters.