Sort/order pull requests by merged date #1600

Activity

1. TPS

   added

   merge

   pull-requests

   sorting

   on Nov 12, 2019
2. eouw0o83hf commented on Mar 18, 2020

   

   eouw0o83hf

   on Mar 18, 2020

   Last edited by eouw0o83hf

   More actions

   This is a really severe gap in usability - every other online scm provider I've used provides this option by default.

   I really need this when sifting through recent PRs while troubleshooting production issues. This feature's absence has cost me a material amount of precious troubleshooting time.

   I know that searching provides a date filter, which is great when you have the time to re-learn how to use the search syntax. But, I should really easily be able to see the most recent merges into the codebase, in order, in order to drive down the time to identifying and correcting production bugs.

   As it stands, GitHub is actively getting in the way of that troubleshooting process and hurting me as a developer.

   👍React with 👍17Reacted by Ustun Ozgur, Adam Grant, Oliver Maksimović, Sadie Perkins, Dan Karney, Grant Iverson, Jeff Hammerbacher, lonewarrior556, Ilse, Serhii Nesprava and 7 more
3. KarneAsada commented on Jun 11, 2020

   

   KarneAsada

   on Jun 11, 2020

   More actions

   While we're at it, can we add the option to change the merged display to use a timestamp? Displaying "merged yesterday" is fairly useless when there are dozens of merges per day.

   👍React with 👍5Reacted by Néstor Soriano, lonewarrior556, escalonn, Nathaniel Clement and Skyler Slade
4. Konamiman commented on Aug 13, 2020

   

   Konamiman

   on Aug 13, 2020

   Last edited by Konamiman

   More actions

   The following script sorts the pull requests by merge date, oldest first (reverse the localeCompare for newest first):

   var issues = document.getElementsByClassName("js-issue-row");
   var issuesArray = [].slice.call(issues);
   
   var sortedIssues = issuesArray.sort(function(a,b) {
       var timeA = a.getElementsByTagName("relative-time")[0].getAttribute("datetime");
       var timeB = b.getElementsByTagName("relative-time")[0].getAttribute("datetime");
       return timeA.localeCompare(timeB);
   });
   
   var issuesContainer = issues[0].parentElement;
   
   issuesContainer.innerHTML = "";
   for(var i=0; i<sortedIssues.length; i++) {
       issuesContainer.appendChild(sortedIssues[i]);
   }

   And the following one displays dates in timestamp format:

   var times = document.getElementsByTagName("relative-time");
   
   for(var i=0; i<times.length; i++) {
       var datetime = times[i].getAttribute("datetime");
       times[i].innerHTML = datetime.replace("T", " ").replace("Z", " ");
   };

   I guess those could be easily converted to TamperMonkey scripts or the like. The problem is that the page updates itself from time to time in order to keep the "human readable" timestamps updated, but at least the sorting is kept.

   👍React with 👍2Reacted by lonewarrior556 and Izzan
5. lonewarrior556 commented on Aug 19, 2020

   

   lonewarrior556

   on Aug 19, 2020

   More actions

   Coming from tfs I honestly cannot believe this is not an option
6. moltob commented on Apr 27, 2021

   

   moltob

   on Apr 27, 2021

   More actions

   Not really the full feature but a small workaround that might just show you the PR you were searching for is to order by updated date. So with a filter like this: is:pr is:merged sort:updated-desc.

   Or in GraphQL:

   {
     repository(owner:"<org>" name:"<repo>") {
       pullRequests(first:100 orderBy:{field:UPDATED_AT direction:DESC} states:MERGED) {
         pageInfo {
           hasNextPage
           endCursor
         }
         nodes {
           number
           title
           updatedAt
         }
       }
     }
   }

   👍React with 👍1Reacted by Jeremy Warren
7. K3UL commented on Apr 29, 2021

   

   K3UL

   on Apr 29, 2021

   Last edited by K3UL

   More actions

   Unfortunately, the last updated is not really a good solution because it just needs any event to count as updated. It does not give an actual timeline of the PR going to a branch.
   For example we have a script that deletes stale branches that have been merged, and it adds an event to the PR, making it more recently updated.
8. chrisclark commented on Jun 21, 2021

   

   chrisclark

   on Jun 21, 2021

   More actions

   Holy moly I think this feature actually exists! I was similarly baffled that this couldn't be done (...and still am), but then stumbled up the "Pulse" page:

   https://github.com/n8n-io/n8n/pulse

   It's not perfect because the date filtering is limited, but it will serve my purposes! Hope this helps someone else.

   ❤️React with ❤️3Reacted by Jacob Summers, Kabeer Vohra and jac

   👀React with 👀3Reacted by Nathan Landis, Denis and jac
9. fzngagan commented on Aug 22, 2021

   

   fzngagan

   on Aug 22, 2021

   More actions

   I've written a ruby script which uses https://github.com/octokit/octokit.rb to list the PRs merged into a branch sorted by the order they were merged into a given branch. Might help someone. :)