Re: AudioGame Collaboration: Should We Do It?
It doesn't matter what the origin branch of a PR is if you're merging it into master.
I.e. it doesn't matter to you at all that I submitted my PR on the master branch. You can merge it into master, a branch called development, or whatever you like. The only thing that matters to you as a maintainer is that you pull the commits you want, and as long as I push nothing else to master before you merge it, which I won't, you'll be fine. Our repositories are entirely separate namespaces, and we have lots of latitude about which commits arrive and where they end up.
So I won't redo my work on another branch. Sorry. But I also won't push to master before you accept the PR, so you're in no danger if you accept it. I just thought that my changes--using a virtualenv, documenting it, and adding a requirements.txt--were pretty standard for modern Python projects, so thought I'd nudge folks in that direction.
Either way, best of luck with this project!
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
