The followings list the pull requests, issues, and comments cited in the paper "Redundancy, Context, and Preference: An Empirical Study of Duplicate Pull Requests in OSS Projects".
| No. | Pull request | Source link |
|---|---|---|
| 1 | angular/angular.js/#4860 | angular/angular.js#4860 |
| 2 | angular/angular.js/#4916 | angular/angular.js#4916 |
| 3 | angular/angular.js/#5063 | angular/angular.js#5063 |
| 4 | angular/angular.js/#7846 | angular/angular.js#7846 |
| 5 | pandas-dev/pandas/#9350 | pandas-dev/pandas#9350 |
| 6 | pandas-dev/pandas/#10074 | pandas-dev/pandas#10074 |
| 7 | facebook/react/#3948 | facebook/react#3948 |
| 8 | facebook/react/#3949 | facebook/react#3949 |
| 9 | facebook/react/#3950 | facebook/react#3950 |
| 10 | facebook/react/#5220 | facebook/react#5220 |
| 11 | facebook/react/#5236 | facebook/react#5236 |
| 12 | facebook/react/#6121 | facebook/react#6121 |
| 13 | facebook/react/#6135 | facebook/react#6135 |
| 14 | kubernetes/kubernetes/#43871 | kubernetes/kubernetes#43871 |
| 15 | kubernetes/kubernetes/#43902 | kubernetes/kubernetes#43902 |
| 16 | emberjs/ember.js/#4214 | emberjs/ember.js#4214 |
| 17 | emberjs/ember.js/#4223 | emberjs/ember.js#4223 |
| 18 | scikit-learn/scikit-learn/#8503 | scikit-learn/scikit-learn#8503 |
| 19 | scikit-learn/scikit-learn/#8517 | scikit-learn/scikit-learn#8517 |
| 20 | scikit-learn/scikit-learn/#8518 | scikit-learn/scikit-learn#8518 |
| 21 | rust-lang/rust/#20380 | rust-lang/rust#20380 |
| 22 | rust-lang/rust/#20437 | rust-lang/rust#20437 |
| 23 | rails/rails/#10737 | rails/rails#10737 |
| 24 | rails/rails/#10738 | rails/rails#10738 |
| 25 | rails/rails/#20050 | rails/rails#20050 |
| 26 | rails/rails/#20697 | rails/rails#20697 |
| 27 | rails/rails/#28068 | rails/rails#28068 |
| 28 | rails/rails/#28399 | rails/rails#28399 |
| No. | Comment | Source link |
|---|---|---|
| 1 | I saw your PR and there wasn't any activity or follow up in that from last 18 days |
https://code.djangoproject.com/ticket/25385 |
| 2 | Oh, Sorry I did not search for a previous PR before submitting a PR | symfony/symfony-docs#4540 (comment) |
| 3 | Ah should have searched first, thanks | symfony/symfony-docs#4897 (comment) |
| 4 | Ah, my bad. I thought I searched, but I must have only been looking at open | symfony/symfony-docs#4897 (comment) |
| 5 | Sorry, I searched before pushing but did not find your PR... | symfony/symfony#10261 (comment) |
| 6 | apologies, I did search before posting (forget the search term I used) but clearly my search was bad... Thanks for finding the dup | angular/angular.js#7846 (comment) |
| 7 | ...This is a dup of that PR. I should have looked harder as I didn't see that one when I created this one... | symfony/symfony#19186 (comment) |
| 8 | Uhm yeah, didn't spot the reference in #21967 | symfony/symfony#21984 (comment) |
| 9 | Argh, didn't see it in the original issue. Need more coffee I guess | nodejs/node#3853 (comment) |
| 10 | I'm glad to hear that. But please link your future PRs to the issues | facebook/react#6135 (comment) |
| 11 | Yeah I will, that's on me! | facebook/react#6135 (comment) |
| 12 | missed the mail for the PR it seems :-/ | kubernetes/kubernetes#43902 (comment) |
| 13 | We are working on this | scikit-learn/scikit-learn#8503 (comment) |
| 14 | I just realized someone was also working on it after I committed | scikit-learn/scikit-learn#8517 (comment) |
| 15 | Since the PR also contains some test cleanup, I'll merge that instead and close this one. But thank you for the efforts, it is much appreciated!! | symfony/symfony#8213 (comment) |
| 16 | After a short discussion internally, we are going to close this one in favour of merging #7666. This is nothing more than the fact that the other PR touches much less files. | hashicorp/terraform#7557 (comment) |
| 17 | Closing this in favor of #10373, which also contains performance improvements. | mozilla-b2g/gaia#10253 (comment) |
| 18 | Looks like #2716 fixed this though the quoting on that one is not 100% right and I prefer your solution... Would you like to rebase yours on top of head to use the '+=(...)' operator? | kubernetes/kubernetes#2694 (comment) |
| 19 | This PR is a subset of PR #16031 | symfony/symfony#16527 (comment) |
| 20 | closing this PR as a duplicate of #5193 (the latter is sent against 2.0 which is the branch to target for bugfix) | symfony/symfony#5075 (comment) |
| 21 | Thanks for the fix. Not sure we want to merge this or wait for #3907 which also fixes it and adds a regression test for all estimators | scikit-learn/scikit-learn#4205 (comment) |
| 22 | Actually, I see that #28026 is at the head of the merge queue right now, so it will probably merge bfore this one, in which case we can just discard this PR. | kubernetes/kubernetes#28037 (comment) |
| 23 | Thank you very much for opening the pull request @xxx. Sadly I have to close it nonetheless because someone already opened one with the same changes before: #5761 | symfony/symfony-docs#5764 (comment) |
| 24 | @xxx The original author of that PR hasn't responded in a week. If you want to fix the tests in your PR, we could merge this one. Your call | facebook/react#6657 (comment) |
| 25 | @xxx do you mind if we close this in favor of #12004 from a new contributor? | servo/servo#11989 (comment) |
| 26 | Replaced by #5067 | ceph/ceph#5018 (comment) |
| 27 | closing in favour of #10582 | elastic/elasticsearch#10499 (comment) |
| 28 | I prefer this behavior (and its simpler implementation) Can you please cherry-pick the test from #20050 | rails/rails#20697 (comment) |
| 29 | along with adding an changelog entry listing both authors | rails/rails#20697 (comment) |
| 30 | Can you credit him in the commit as well after you squash and rebase | rails/rails#24719 (comment) |
| 31 | Other PR didn't get updated today and the failures were annoying on new PRs. | facebook/react#5236 (comment) |
| 32 | Could you jump on #3082 and help us review it? | angular/angular.js#2835 (comment) |
| 33 | Please work with @xxx to test his code once he fixes the merge conflicts | ansible/ansible#4034 (comment) |
| 34 | Made a minor note on the other PR to include one of the improvements | nodejs/node#10753 (comment) |
| 35 | Looks like they took my advice and used proc terminate() so another package was not needed. Thanks for catching duplicate, but at least it was not a waste. :) | symfony/symfony#5457 (comment) |
| 36 | it probably makes sens to just center around a single effort | emberjs/ember.js#3261 (comment) |
| 37 | No need to do the same thing in two PRs | kubernetes/kubernetes#46913 (comment) |
| 38 | Oops! Sorry, did not mean to double up | pandas-dev/pandas#12576 (comment) |
| 39 | The pull requests are different, so maybe it is good there are two. | facebook/react#3948 (comment) |
| 40 | Pick me! Pick me! I was first! :) | cocos2d/cocos2d-x#2540 (comment) |
| 41 | I looked at some awesome code that xxx wrote to fix this issue and it was so simple, I just did not fully understand the issue I was fixing. | facebook/react#6121 (comment) |
| 42 | @xxx, btw, it is a good idea to comment on an issue when you start working on it, so we can coordinate better and avoid duplication of effort | angular/angular.js#15106 (comment) |
| 43 | Thanks for your PR but this fix is already merged in #20610 | ansible/ansible#15608 (comment) |
| 44 | 'already' implies I submitted my PR later than that, rather than nearly a year earlier ;) But at least it’s fixed. | ansible/ansible#15608 (comment) |
| 45 | sorry, sometimes a PR falls in the cracks and a newer one gets the attention. We have improved the process in hopes to avoid this but we still have a big backlog in which these things are present. | ansible/ansible#15608 (comment) |
| 46 | I wish there has been some automated method to detect pending PR per file basis. This could save lot of work duplicacy. ... | joomla/joomla-cms#8394 (comment) |
| 47 | It’s strange that GitHub isn't complaining about this, because it’s an exact dup of #5131 which was merged already | moby/moby#5226 (comment) |