It sounds like what you have ended up with is dev and master as effectively forks of the code base, rather than branches: features are merged to each more-or-less independently, and there is no process to keep them in sync.
Most workflows with multiple long-lived branches instead treat one branch as the "future" of the other. For instance, features ...
If you've never seen or heard about snow in your life, and I put in in the middle of a snowy field, you're going to be asking yourself things that seem naive to someone who has a modicum of experience with snow.
That is what you've done here. You come from what most of us would call a very outdated concept, you're on the cusp of entering our world (i.e. that ...
No, you can't really split a commit into multiple commits across different repositories. The next best thing is that you can extract and push the history for a directory with git subtree, or that you can mount a repository as a git submodule.
But neither of those approaches is an appropriate solution in your scenario.
Your database is a centralized resource. ...
It just takes time for developers to adapt to new possibilities.
Since this question was asked, github has gained acceptance by major open source project.
github/gitlab has made working together with pull requests a lot easier.
saves time t
to learn g individual contribution guidelines
for millions of developers/users (u)
who invest time (i) to improve, ...