Review my github workflow

[Mario F.]

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:

.
├── bash/
│   └── ppenv
├── docs/
│   └── ppenv
├── ksh/
├── LICENSE
├── man/
│   └── ppenv.1
├── posix/
├── python/
├── README.md
├── sh/
└── zsh/

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.

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.

[MutantJohn]

It sounds hard to enforce that preference for shells at a code level.

[Yarin]

Is there a reason you have so many script support levels? It would be easier to choose one particular compatibility and stick with that for everything.

[Mario F.]

It's mostly a dump place for scripts and I haven't thought it over very well yet. You are probably right. I'd expect most scripts (at least the ones I am going to write) will be bash or zsh scripts, which are the only shells I use (mostly zsh these days). Having someone put a korn script there will do me no good.

Meanwhile I have been testing the branch approach and I trashed it. It's too inconvenient. It forces two pull requests for no good reason. The first, from the local changes to the develop branch is ok. But the second from the develop to Master is just unnecessary extra work that benefits no one. Git-Flow isn't appropriate here because of the simplicity of script development. So any pull requests will be done straight to Master.

I think I will be dumping those other shells too and keep just bash and zsh (and python). I'll maintain the the last compatibility rule described on the README though. I'll be updating it tonight. But essentially, if you do a bash script that is also zsh, put it anywhere you wish as long as you properly signal the other directory with a dot file.