GitLab.com co-founder here. Forking should work fine in recent versions of GitLab (6.x). You can fork a repo belonging to someone else and then create a merge request (the properly named version of the GitHub pull request).
Alternatively make develop the default branch that everyone sees when visiting the project. The downside is that anyone who clones it will get an unstable branch by default but all pull requests will go to the develop branch by default too.
You probably will merge this pull request on master, so you can checkout just this specific file again, from master, on your branch, just type: git checkout master — xcodeproj/project.pbxproj git commit -m “removing a file from PR” git push origin {YOUR BRANCH}
You can get all pull requests (closed, opened, merged) through the variable state. Just set state=all in the GET query, like this-> https://api.github.com/repos/:owner/:repo/pulls?state=all For more info: check the Parameters table at https://developer.github.com/v3/pulls/#list-pull-requests Edit: As per Tomáš Votruba’s comment: the default value for, “per_page=30”. The maximum is per_page=100. To get more than 100 results, you need … Read more
In general, you can list the files changed between any two commits with git diff –name-only : How to list only the file names that changed between two commits? The problem here seems to be determining the ‘merge base’. If all branches originate with master, then you could do: git –no-pager diff –name-only FETCH_HEAD $(git … Read more
The rule of thumb that we use (which is here some where on Stack Overflow) is “branches are for work, tags are for history”. Whenever a branch is merged (most likely into master) we tag the merge point using the name of the branch with the prefix “branch” (e.g. branch-topic). Then delete the branch. If … Read more
You must create templates on the repository’s default branch. Templates created in other branches are not available for collaborators to use. You can store your pull request template in the repository’s visible root directory, the docs folder, or the hidden .github directory. Pull request template filenames are not case sensitive, and can have an extension … Read more
Note that Bob doesn’t have to squash his commits when he is making a GitHub PR. Since March 2016, you can leave that operation to the maintainer (you) accepting your PR. See “Squash your commits” and its new documentation This is a new option which lets you force commit squashing on all pull requests merged … Read more
As long as the original author has clicked the checkbox in the bottom right: If that box is checked, then you can push back to the original branch without needing to add a remote by using: git push git@github.com:user/repo local_branch_name:remote_branch_name This is particularly useful if you’re using a tool like hub where you can check … Read more
The answer given by svick is not correct. It is possible. There’s git request-pull which is part of the Git suite. Using that command line tool, you could create a pull request that could be sent per E-Mail. Example: your origin holds a branch master. Now you create a local bugfix branch fix, implement the … Read more