I would like to use git annex with github. Here what I did:
- Create github directory "a". Added all the special remote and git annex files. Pushed them to the "a" using "git annex sync."
- Fork the repository on gihub to "b". Clone it and enable remote and I could pull annexed files.
- Added repository "a" as "upstream" tracking remote to "b".
- Created a second special remote for "b". Added new git annex files to it. Used "git annex sync origin" to push the changed files to the forked repository "b".
- Now I would like to create a pull request. What are branches I should create pull request for? a:synced/git-annex vs b:synced/git-annex? Or, a:synced/git-annex vs b:git-annex? Do I need to create separate pull request for the "master"?
Thanks for the help.
Your pull request should be for the branch you changed. In this case, the
masterbranch. This is the same as adding files to a regular git repository and making a pull request for that.The changes that git-annex makes to the
git-annex branchcan either be ignored by the person who merges your pull request, or they could opt to fetch your git-annex branch and let git-annex auto-merge it for them. A manual review and pull request of thegit-annexbranch is not likely to be productive. Whether they need to merge yourgit-annexbranch into theirgit-annexbranch depends on whether git-annex's information about eg, locations of file contents needs to be passed along with your pull request.Note that GitHub does not support using git-annex to upload the content of annexed files to it. (GitLab does support this.) This GitHub limitation may cause problems with this kind of workflow.