The question is most probably for @eirannejad. And my question might feel simple or stupid to git addicts, but that might serve other new to code people.
I start by forking the pyrevit git.
From my fork, I create a branch with a name that states what I am working on (should I branch in the first place?)
I create new stuff, modify some existing ones, then commit to that branch.
After that, I create a Pull request aimed towards the pyrevit source repo… But I never know which branch to PR it to: master, develop, feature…
And if I keep on doing some mods, but to some other tools, topics, I tend to branch again but from my previous branch. Is that a correct way of doing it?
So the more general question:
how would you like people to contribute to pyrevit in terms of git workflow so that it makes maintainable easier?