Idea logo

The IntelliJ IDEA Blog

The Capable & Ergonomic Java IDE by JetBrains

Early Access Program

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


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).


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.


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!

Comments below can no longer be edited.

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

  1. Antoine Kurukchi says:

    October 17, 2018

    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:

    October 17, 2018

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

    • Edoardo Luppi says:

      October 18, 2018

      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:

    October 17, 2018

    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. Gabriel says:

    October 17, 2018

    Please fix this

  5. Erik Ghonyan says:

    October 17, 2018

    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.”

    • Dmitriy Smirnov says:

      October 18, 2018

      Maybe you have Single-SignOn enabled? Then you need to authorize the token for SSO.

      • Erik Ghonyan says:

        October 22, 2018

        So I checked and I don’t see the SSO button on my tokens. I also tried to load an individual pull request manually (an HTTP request with the “Authorization: Bearer [my-token]”) and it worked.
        I’ll try to get the logs and open an issue. Thanks!

  6. Palanivelrajan Balasubramanian says:

    October 17, 2018

    Any plans to support this for bitbucket?

  7. Palanivelrajan says:

    October 18, 2018

    Do you plan on adding similar support for bitbucket?

  8. Javier San says:

    October 18, 2018


  9. Valentin Slawicek says:

    October 18, 2018

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

  10. Dmitry says:

    October 18, 2018

    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:

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

    • Zlata Kalyuzhnaya says:

      October 18, 2018

      Hi Dmitry! Unfortunately, for now, we don’t plan to change the layout. Please consider as a workaround the ToolBox App. It now displays all required information such as build number, release notes, build highlights.

  11. Martin Kuhn says:

    October 18, 2018

    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)

  12. Barclay says:

    October 19, 2018

    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

  13. abt says:

    October 19, 2018

    Would love to have integration like that with Bitbucket.

  14. Andrzej says:

    October 22, 2018

    On linux I received the error:

    java.lang.UnsatisfiedLinkError: /home/…./bin/ cannot open shared object file: No such file or directory
    at java.lang.ClassLoader$NativeLibrary.load(Native Method)
    at java.lang.ClassLoader.loadLibrary0(
    at java.lang.ClassLoader.loadLibrary(
    at java.lang.Runtime.load0(
    at java.lang.System.load(
    at com.intellij.util.lang.UrlClassLoader.loadPlatformLibrary(
    at com.intellij.openapi.wm.impl.GlobalMenuLinux._loadLibrary(
    at com.intellij.openapi.wm.impl.GlobalMenuLinux.(
    at com.intellij.openapi.wm.impl.IdeMenuBar.installAppMenuIfNeeded(
    at com.intellij.openapi.wm.impl.WindowManagerImpl.showFrame(

  15. Kousha Talebian says:

    November 28, 2018

    I am also getting

    “Cannot load details. Can’t get pull request. Couldn’t parse GitHub response.”

    I do not have Single Sign On enabled. How do I access the logs for this request to get more details as to why this is failing?

  16. lippi says:

    December 5, 2018

    Any updates about supporting Bitbucket in the future to handle pull reqeusts similar?

  17. Gregory Czerwinski says:

    December 28, 2018

    We are using a GitHub Enterprise on premise installation and I cant see PR option in VCS tab for it with newest IntelliJ(2018.3.2). Do you know if such installations are supported ?

    • Dmitriy Smirnov says:

      January 9, 2019

      Yes, it is supported. But you need to have your account for GitHub Enterprise registered in Settings | Version Control | Github for this to work.

  18. Gregory Czerwinski says:

    December 31, 2018

    We are using GitHub Enterprise on premise installation, do you know if it is supported?

    • Dmitriy Smirnov says:

      January 9, 2019

      Yes, it is supported. But you need to have your account for GitHub Enterprise registered in Settings | Version Control | Github for this to work.

  19. Kyle R says:

    January 2, 2019

    Is there any way to get the client to ignore merges in the branch? I’m seeing some commits related to a different branch that was already merged back into the mainline branch. I don’t see these commits in of Github’s web view, but they appear in the IntelliJ GitHub Pull Requests tool.

    I’m currently using PHPStorm 2018.3.2

  20. Ruslan says:

    January 3, 2019

    When viewing the changed files of the pull request as shown in rightmost column of the first and second pictures, is there a way to open the source file in the codebase? When I right-click the file, it only gives me the “Show Diff” option. It would be nice if there was also a “Show Source” option as well.

    • Dmitriy Smirnov says:

      January 9, 2019

      Default shortcut which is used across the entire IDE for Jump to source – F4 – works.

      • Ruslan says:

        January 9, 2019

        I confirmed that pressing F4 works. It would be great if a future minor update of IntelliJ added the ability to do this using the mouse as I described in my previous comment. Thank you.

  21. Powel says:

    January 25, 2019

    If you want to see pull-request from BitBucket Server, you can check out myButbucket plugin:

  22. Laura says:

    April 17, 2019

    An obviously large component of pull requests is reviewing them. It would be good if we could leave inline comments on the pull request via the IDE.

    • Kush says:

      May 6, 2019

      I second this, reviewing PRs should be easier. Would love to see existing pull request comments inline within the IDE, and be able to make comments, as well.

    • Boris says:

      May 30, 2019


    • Zach Bimson says:

      June 12, 2019

      + 1

    • James Brauman says:

      July 31, 2019

      That would be amazing!

      • Vedavidh Budimuri says:

        December 30, 2019


    • Vedavidh Budimuri says:

      December 30, 2019


  23. shlomik says:

    June 27, 2019

    Thanks for the feature.
    Missing critical abilities:
    1. Reviewers were not imported correctly (got 1 of 3)
    2. Comments of reviewers are not visible.
    3. Reply to comments is NA of course.
    Please consider adding these, otherwise there is no real reason to use this PR integration.

    • stan says:

      September 21, 2019


    • Pavel Lechev says:

      December 3, 2019

      Given that this functionality will involve potential changes to the editor, to start with, perhaps we can have some indication (i.e. icon badge) in the file tree to the right which shows the files that have comments on them and ability to click the file and navigate to the first comment in it on Github.

    • liu haoran says:

      April 24, 2020


  24. Alexander Kim says:

    October 26, 2019

    Does 2019.2 has this feature already?

    • Dmitriy Smirnov says:

      October 29, 2019

      The list of PRs, with the ability to view the changes and PR status, as described in the post, is available since 2018.3, so yes 2019.2 has it.

  25. splintor says:

    November 25, 2019

    > We plan to add actions such as merge, close, comment, and more in the forthcoming releases.

    Any progress on that? ETA?

    • Dmitriy Smirnov says:

      November 25, 2019

      The feature is close to finishing, but hasn’t made it to 2019.3.
      So we aim at 2020.1.

  26. john says:

    December 20, 2019

    Does Community version support create PRs if it does how to it?

  27. Min says:

    April 20, 2020

    When I open a pull request the merge button is greyed out and it says “Loading pull request status…” but it hangs there. How do I fix this?

Discover more