Why is github proposing "compare & pull request" (green button) when I'm the only contributor/maintainer in the repository? Like shown in this screenshot:
I find it strange that I should ask myself for a pull request. Shouldn't I just be able to merge the branch without asking for a pull request?
Thanks!
Pull requests can still be useful for keeping track of your own work, leaving notes, and letting other developers discussion, review, and follow it.
This is all optional though, if you prefer you can just merge locally.
Related
I have a git enterprise in my company and we have a system like this documentation for review the pull request before merging into master. But here is coming a problem. People are reviewing when the branch is still in progress.
How I can do, to remove review after a new commit was done in a branch?, or check that the review is the last thing before have the button of merge pull request green?
Thanks!
You can add a tag "work in progress" on the pull request.
https://help.github.com/articles/working-with-tags/
Does anyone know of a way in GitHub to see pull requests were I am mentioned and either I have not yet commented or commits have been added since I last commented?
If you watch a repository like this, you'll be notified by everything that happens on that particular repo:
New commits will appear on your on-site dashboard and comments on commits/issues/PRs (by the way "PR" stands for "Pull Request) as well as opened/closed/merged PRs and issues will come up both by e-mail and on your dashboard.
We have just moved across to Targetprocess. It looked like it had good github integration, when a commit to that branch has "id:[storyid]" in the title it will detect it and setup the reference.
The issue we have is that we all use forks and create pull requests to merge stories / changes back into the main organisations repository. Github will not allow us to change the title (that I can see) and Targetprocess does not look at the comments section for the id:[storyid].
Is there a way to be able to change github to allow the merge commit to have the id:[userstory] text in the title?
https://help.github.com/articles/merging-a-pull-request/#merging-a-pull-request-using-the-github-web-interface states that GitHub allows to change message while merging PR via browser interface.
The same applies to the command line interface.
GitHub explains you can fork, modify, commit, push and trigger a pull request. They also explain that you can still modify, commit, push and the request is updated on the website.
I would like to know if it is possible to do the exact same thing but not being the author of the fork? I am the owner of a repo with pull requests I would like to correct myself but still discuss afterwards... I was trying to push my changes into the author's repo (thinking some right access would be calculated) but the access is denied.
When creating a pull request (PR) on GitHub, you can select the option that maintainers are allowed to commit changes to your PR. You can also do this after the PR is already created: In the detail view of the PR, on the lower right, under "Unsubscribe", "participants". So if you want to commit to a PR of someone else on a GitHub repository you own: Ask them to give you this permission.
From the GitHub help pages: "Only pull request creators can give upstream repository maintainers, or those with push access to the upstream repository, permission to make commits to their pull request's compare branch." (Allowing changes to a pull request branch created from a fork)
Unfortunately, as far as I know, in order for someone to commit to the PR, you would have to give them write access to the repository and can't just selectively give them write access to the PR.
Official GitHub support answer at this date
It would be up to the owner of the forked repository to decide if they
want to pull your changes into their fork.
You would modify their Pull Request and merge it into your repository.
You could then request them to pull down the changes you have made
into his fork which would synch his fork with yours.
On GitHub, I can see the history of commits of a file under .../commits/master/filename. What I want to know is, assuming these changes were merged into master via Pull Requests, what Pull Request did the change come from? Is there an easy way to do that?
Since Oct. 13, 2014, this should be easier:
Linking merged pull requests from commits
We've been including the containing branches and tags on commit pages to give you more context around changes. Now, commits in a repository's default branch will also show you the pull request that introduced them.
In the pull request, you can see the discussion around why the commit was introduced, and get a clearer picture of the reason for the change.
As always, if you know the commit SHA, you can skip the commit page and search for the pull request directly.
For instance:
You can see for the file hakimel/reveal.js/plugin/markdown/markdown.js, my contribution now comes with a reference to the PR #734 it originated.
Note however that:
neither GitHub Get single commit API, like https://api.github.com/repos/hakimel/reveal.js/commits/f2097417daca80b2caaed2661ee646e861d789c8
nor GitHub Get a commit API, like https://api.github.com/repos/hakimel/reveal.js/git/commits/f2097417daca80b2caaed2661ee646e861d789c8
will include the reference to the PR...