#IJPL-187199 Fixed
#IJPL-186195 Fixed
Cause of which is a threading exception on loading `.getContent()`
(cherry picked from commit eec980bbaf107e2caa4f08c5150e74b773e0593b)
IJ-CR-163488
GitOrigin-RevId: 263439b1b91f620222c5d27739485231164173fd
Didn't check every single usage, but in an ideal world,
this user should never leak into an API request.
Erroneous usages of the FAKE ghost user should be found when reported
and replaced with `null`, because in this case it's apparently
possible not to have a user assigned at all.
To be abundantly clear: this FAKE ghost user replaces github.com/ghost
in case one does not exist on the server.
(cherry picked from commit 6a1f48e6751992463cbe5c43b740ef2ab0f999fa)
IJ-CR-161085
GitOrigin-RevId: 8109653900f7394813aaba8ac2776c86eaeb143a
GH decided to break links by having them repurposed as a deprecation warning.
Explicitly marking our query as 'advanced' is enough to ignore this.
#IJPL-180348 Fixed
(cherry picked from commit 3cee15779eacc58233a3b40b15aa61ff054a3891)
IJ-CR-160675
GitOrigin-RevId: 2c582985f3da00c813c78e23c3e724917e2c1191
The existing gitlab.community and github.community modules that describe community versions of plugins with less functionality included do still exist intentionally. This is required for external developers to be able to build IDE from community project sources and get both plugins working there out of the box. Thus community plugins are still listed in IdeaCommunityProperties and PyCharmCommunityProperties. This part is only required for third-party folks. As for internal builds, they employ a build context produced by `org.jetbrains.intellij.build.IdeaUltimateBuilderKt.createBuildContextForCommunityProduct` which in turn prefers github.ultimate and gitlab.ultimate plugin distributions over community ones
(cherry picked from commit e8233c7133d63abe3aefa684cc57ed9bad9fee64)
IJ-CR-156816
GitOrigin-RevId: c7058bba3734d4509a66d48b338466f5e0e7b05d
IJ-CR-156508
to make run configurations that employ flat classloader load ultimate plugin version in ultimate IDE, not the community one
(cherry picked from commit 9b2210eafc67d35af91b22a0e5d9b85a05adc5bd)
GitOrigin-RevId: 55dcbaf8581ad585611b676d5c39d2318cb8a7c9
Most of these fail because they're missing the test environment
Only those in GHPRTimelineMergingModelTest need proper fixing still
GitOrigin-RevId: 3fec5b7d0b3f710743f18e173065f34f1f2d9759
Implemented for dialogs with yes/no/cancel, yes/no, ok/cancel actions. Any other dialogs with custom actions will return undefined exitActionType
Merge-request: IJ-MR-154390
Merged-by: Vera Petrenkova <Vera.Petrenkova@jetbrains.com>
GitOrigin-RevId: dd030c0a4a98c385d30c3710b3a063f500bb400e
- Fix missing host check for getting the API URL.
- Add missing tests for API URL expectations.
GitOrigin-RevId: a34e93794e02a7d2e87af87f95fbb2c2346967dc
#IJPL-175710 Fixed
This is caused by `... on Bot` not being allowed for `PullRequestReviewers` before GitHub 3.11.
The newly added tests can confirm this mistake.
GitOrigin-RevId: 87015863c0c8c0cd581f98eeefa5ae45adad34e8
#IJPL-176927 Fixed
Turns out: we all make boolean logic errors every once in a while, no exceptions.
follow-up: f449ea4351689c3dac3b0ea23327addc30e25c1e
GitOrigin-RevId: 9ab72e969a704fa346e76c69d14cfba068bde0ee
#IJPL-174769 Fixed
Data-residency instances act like GH Enterprise servers, except that API
URL is not under the regular https://{host}/api/foo
Instead, it's under https://api.{host}/foo.
GitOrigin-RevId: f363eb431ca4d0246118e8e5af6b1cef9c61ba05
saving project configuration as it's done in regular commit
see com.intellij.openapi.vcs.actions.commit.CheckinActionUtil#performCheckInAfterUpdate
performCheckInAfterUpdate can be reused completely, it can be done as a separate task
GitOrigin-RevId: 5885dbb30e6f4008dad211dc15090f67464d1328
