IntelliJ IDEA 2018.3 EAP: GitHub pull requests and more

We are excited to announce that the upcoming IntelliJ IDEA 2018.3 will come with initial support for GitHub pull requests, along with a couple of other features worth talking about in detail.

GitHub Pull requests

Now you can view all pull requests from your GitHub repository as a list inside the IDE. They are available in the brand new GitHub Pull Requests tool window. Select Main menu | VCS | Git | View Pull Requests and view the state of a PR, current label, and assignee, if any. In the right pane, you can view the altered files and use the diff to preview the changes.

We plan to add actions such as merge, close, comment, and more in the forthcoming releases. For now, you can create a local branch from a PR via the context menu and then merge it as a regular branch. From the same context menu, you can quickly open a pull request on github.com.

VCSGitHubPullRequests

You can promptly find the PR you need by searching by state, assignee, author, after, before, or sort by. By the way, autocompletion is available in this search field as well.

Screen Shot 2018-10-16 at 19.31.20

This is just the beginning as we plan to extend this functionality with the upcoming releases. Stay tuned for more updates!

Speaking of improvements in VCS support, the Back and Forward navigation actions are now supported in the VCS Log. Previously, we made it possible to navigate from the commit hashes to the commit in the VCS Log tab. Now we’ve extended this functionality and while the focus is in the VCS Log, you can use the editor actions Cmd-] / Cmd-[ for navigation. Alternatively, select Navigate | Back / Forward from the main menu. The same navigation actions work after you use the ‘Go to hash/branch/tag’ action (cmd+ F on macOS, ctrl + F on Windows and Linux).

VCSNavigation

While in the VCS Log, you can also use left and right arrow keys to go to the child or parent commit. These new actions play nicely with merge commits as well.

VCSNavigationChildParent

As for the JDK, it’s been updated to v1.8.0_152-release-1343-b12.

  • Resolved a keyboard issue in the quick search popup which blocked all keyboard events JRE-252.
  • Some system DLLs will be shipped with JFX builds because JFX building was switched to Visual Studio 2017 JRE-991.
  • Repaired the regression caused by the fix for IDEA-185285: JRE-981.

For more details about the changes in this build, check out the IDE release notes and the JRE release notes.

Download the fresh IntelliJ IDEA 2018.3 EAP build now! We can’t wait to hear your feedback on these improvements, so please share your thoughts and ideas via the discussion forum, our issue tracker, or on Twitter!

Happy Developing!

About Zlata Kalyuzhnaya

IntelliJ IDEA Marketing Manager at JetBrains. twitter: @ZlataKalyuzhnay ‏
This entry was posted in EAP Releases and tagged , . Bookmark the permalink.

22 Responses to IntelliJ IDEA 2018.3 EAP: GitHub pull requests and more

  1. Antoine Kurukchi says:

    Love the new way of informing customers of what has changed between EAPs. Found it very easily through Jetbrains toolbox. Thanks

  2. Oleksii Vynnychenko says:

    Do you plan to do the same level of integration with Gitlab ?

    • Edoardo Luppi says:

      I think that this is an experimental feature, and that they’ll refactor it to a public usable API in the future, as they always do. So that we can build our plugins

  3. TheBestPessimist says:

    I think Pull Requests should be integrated in the Version Control dialog instead of having a new one. i expect that pull requests will have functionality for bitbucket and others in the future so this (being available with alt+9) feels more natural.

  4. Erik Ghonyan says:

    It loads the list of pull requests but when I click on an item it shows “Cannot load details. Can’t get pull request. Couldn’t parse GitHub response.”

  5. Palanivelrajan Balasubramanian says:

    Any plans to support this for bitbucket?

  6. Palanivelrajan says:

    Do you plan on adding similar support for bitbucket?

  7. Javier San says:

    Awesome!

  8. Wow, I guess it is now time to release a dedicated VCS client as standalone application.

  9. Dmitry says:

    Could you please consider changing layout of the “nextversion” page a bit to have the latest build info visible “above the fold”?

    Here is what I see when checking the page for updates with the browser content area width of 1280px:
    https://i.postimg.cc/T2rgTt1N/nextversion.png

    Every time I have to scroll down to see if a new build is available.

  10. Martin Kuhn says:

    After installing this latest version the cpu load is significantly increased (it influences the editing behaviour so I switched back to 2018.2.5 for working)

  11. Barclay says:

    Great addition. Can you add the option to create issues from within the IDE? This would help massively to not break flow by switching context to the browser.

    I did ask for a related version of this a while back, but would probably be best tied into your github work. #IDEA-163804

  12. abt says:

    Would love to have integration like that with Bitbucket.

  13. Andrzej says:

    On linux I received the error:

    java.lang.UnsatisfiedLinkError: /home/…./bin/libdbm64.so: libdbusmenu-glib.so.4: cannot open shared object file: No such file or directory
    at java.lang.ClassLoader$NativeLibrary.load(Native Method)
    at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1941)
    at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1824)
    at java.lang.Runtime.load0(Runtime.java:809)
    at java.lang.System.load(System.java:1086)
    at com.intellij.util.lang.UrlClassLoader.loadPlatformLibrary(UrlClassLoader.java:350)
    at com.intellij.openapi.wm.impl.GlobalMenuLinux._loadLibrary(GlobalMenuLinux.java:489)
    at com.intellij.openapi.wm.impl.GlobalMenuLinux.(GlobalMenuLinux.java:123)
    at com.intellij.openapi.wm.impl.IdeMenuBar.installAppMenuIfNeeded(IdeMenuBar.java:546)
    at com.intellij.openapi.wm.impl.WindowManagerImpl.showFrame(WindowManagerImpl.java:458)

Leave a Reply

Your email address will not be published. Required fields are marked *