pull-request

I am looking for some command which tells me number of files committed in a single pull request. I would like to know count of files in a single pull request individual from beginning. Question explained in real life scenario: Let's say for some myProject someone raised a pull request number 100 which has changes in 15 files. I am looking for a command which list all pull request from 1 to 100 with count of changed files. Please answer wrto Windows 7. i.e. PR Number 100 has changes in 10 files PR Number 99 has changes in 5 files PR Number 98 has changes in 6 files PR Number 96 has changes in

My team uses pull requests internally for code-reviewing the application we maintain, but when it's time to merge a commit, we just push directly to master . We're all repo collabs anyway, and by not using the pull request to merge code, we avoid polluting our commit history with merge commits. Since the app is internal to our team, no one else is affected. What I want to know is, can I amend my commit message with something like "closes PR #30" and have github automatically close the pull request for me? I know you can use commit messages to close issues, so I'm hoping there is something

I have a project up on github, which an organization on github has forked. Can i push my code downstream to the organization's fork? I tried doing it, but was not able to. I would like to know if i can send a pull request downstream? GitHub does allow this, and it's actually pretty easy to do, although I didn't find it very clearly-documented. The short of it, is that when you navigate on Pull Requests > New Pull Request from the GitHub UI, you get taken to the "Compare" page. In the drop down to the left you can select your own branches, OR you can type in a branch on another user's repo

I've cloned a project, and pushed a branch with just a renamed readme file to README. I am trying to create a pull-request on the command line, just to try PR from here instead of a website. $ git request-pull origin/master origin readme:readme The following changes since commit 51320a3a42f82ba83cd7919d24ac4aa5c4c99ac6: first commit message are available in the git repository at: git@github.com:example/com:example.git readme for you to fetch changes up to 891c05c5236341bcbe33ceddc415ae921ee42e44: second commit message ---------------------------------------------------------------- Simone

I know about using branches for multiple pull requests, that's fine. But what about this scenario: Dave is the upstream repo, master branch "Dave/A" Satish forks the repo, creates branch B, and sends a pull request against Dave/A Satish then creates branch C from Satish/B, and let's assume that C requires B Satish wants to create another pull request, this time for branch C I've found two conflicting sets of advice (but perhaps the dependency on B is different) Advice from GitHub seems to say C should be applied against A: Changing the base repository changes who is notified of the pull

I have gitlab installation running, and I have a repository with library that I want to share with my friends, I can't understand what is the flow of sending pull request in gitlab.. The user can't fork my repository, he can't access my project (unless he is my on team.. which is weird..) and the merge request can be from one branch to another in my repository.. How it works in gitlab? GitLab will have forking as of version 5.2. Cross repo pull requests will soon follow. Fork pull request: https://github.com/gitlabhq/gitlabhq/pull/3597 GitLab.com co-founder here. Forking should work fine in