Does anyone have an example of adding the status of a pull request to a markdown doc? I am trying to create a readme with a list of PRs, and I want a badge next to each PR with the status of that PR, merged, opened, closed. I haven't been able to find any docs on doing this, but I can't imagine I am the first one to want this feature.
On the Github wiki, issues and other markdown area of your repository, you can link PRs. Hoovering the mouse above the link shows its status. I do not see any other automatic way of showing these information
Related
I created a repository on GitHub and want to add a couple of friends to review my pull requests.
I used this source and when I enter the names of some GitHub users the Reviewers bar stays empty.
How to add arbitrary reviewers to my GitHub repository?
You can simply send the pull request link to your friends, then they can click the files changed button at the top:
Then, they can look through the diffs, and click the blue plus button on any line where they want to leave a comment:
Then they can click it, and add a comment and start a review:
You don't need to formally invite them since anyone that can read the repository can review pull requests. If you want to give them a github notification, you can mention them in the comments.
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.
There are a plenty of Pull Requests on GitHub. Each pull request goes through code review process by one of a few developers. Is there a way to filter out only those pull requests, that has been reviewed by a specific user?
I've tried multiple filters:
build-in GitHub is:open mentions:nattfodd - shows only PRs where there are replies to nattfodd's commentaries, skips PRs with nattfodd's commentaries, but w/o replies to them
simply typed nickname to search field - same behavior
Is it even possible to get what I want?
Github is already providing a very powerfull search API, which includes
Search by a commenter within an issue or pull request.
You can use the filter in the following way: commenter:nattfodd.
For more information please refer the official page here.
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 provides notifications via mail or web, based on watched repos. But is there a way to get more in detail? Like only watch a specific pull requet or assigned issue? I feel like i get spammed from comments on other pull requests that have nothing to do with me.
Update Nov. 2020: you now have "Custom notification controls"
This week we are giving you more control over the types of content that you are notified about on GitHub:
Watching a repository can often be a double-edged sword.
You want to stay up to date with a project, but if you have a specific interest or role within the community, you have no choice but to subscribe to updates on everything.
No more.
Beneath the watch button, you’ll find that we have made a few changes: we’ve made the language clearer so you know what you’ll receive updates about, we’ve made the interface more accessible and, we’ve introduced a new custom category.
Within this, you can select the types of content you would like to be notified about.
Do you focus on code review? Limit your notifications to pull requests.
Are you a community manager? Select Discussions.
As new types of notifications are added, you’ll find them in this menu.
You’ll find these controls on all repository pages and on your watching page where you can customize notifications for repositories you already watch.
Update May 2019: you now have "Custom thread subscriptions"
You can now limit the types of notifications you receive for any issue and pull request to be specific to merge, reopened and/or closed events.
That should allow to further control the amount of emails received.
Update July 2017: you now can declare in the GitHub repo a code owner.
Any pull request touching a file managed by said code owner will trigger a notification to that person.
See "Repo owner automatic notification after updating a pull request"
2015: Yes, for instance, for a specific issue on a project (issue 2595), you can register by clicking the "Subscribe" button at the right side of the page (since 2015).
Once clicked, it will appear as "Unsubscribe" (for you to click if you don't want any more notifications)
So you don't have to watch the all repo, you can subscribe only to specific issues.
Not sure if this has changed, but now there's a subscribe button in the top right corner:
https://help.github.com/articles/subscribing-to-conversations/
first disclaimer, Im part of the team at zigi.ai
Instead of getting notifications for every activity on Git via email or web, Zigi integrates with your Github to learn your pull request activity,
Filters the information and sends you actionable notifications on your pull requests activity (from all repos) that is relevant to your work directly from Slack.
Once a PR is created in GitHub, Zigi manages the entire workflow:
Gathers all the communications related to a PR- that's relevant to
you
Tells me which PRs are waiting for my review from all repos
Shows which of my PRs are waiting for a teammate's review and for how
long
Makes it easy to ping teammates to remind them (without feeling
awkward about bothering them)
Lets me add reviewers
Tells me when a PR is stuck or open for a long time
Helps me make sure the code owner approved
See here an example of a Slack message with filtered notification for pull request