Kirill Likhodedov

Created August 06, 2018 12:16

Ah, you're right: it is not that straightforward there. If a customization is defined, it is in some cases executed instead of the base code. See the GitPushOperation class. So you might need to pr...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Listen for Git push events from IntelliJ plugin

• 1 vote

Created August 06, 2018 07:48

Please try GitPushProcessCustomization#executeAfterPush(). You'll have to check the push results, whether they are successful or not.

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Listen for Git push events from IntelliJ plugin

• 0 votes

Created July 19, 2018 19:52

And how do you execute `git push`? The best way to do it is to call `Git.getInstance().push()` – it will return a GitCommandResult, which you can analyze.

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Knowledge require for plugin development in Intellij IDEA

• 0 votes

Created July 12, 2018 13:13

The step #2 is not quite clear to me. What kind of request are you sending to GitHub after pushing? Or do you mean that you want to analyze the output of the `git push` command which was executed o...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Knowledge require for plugin development in Intellij IDEA

• 1 vote

Created July 04, 2018 10:46

Hi Sanjay. What do you mean by "automatically call GitHub Commit window"? Do you mean programmatically? If so, please check if AbstractVcsHelper.commitChanges() works for you. Don't hesitate to ask...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Knowledge require for plugin development in Intellij IDEA

• 1 vote

Created October 22, 2017 18:08

Then maybe you should try the second approach that I've mentioned above: listen to directoryMappingsChanged(), transfer execution to another thread and call getRepositoryForRoot() for every reposit...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Ensure initialization of GitRepositoryManager before doing plugin operation

• 0 votes

Created October 22, 2017 17:54

What do you mean by "debounce"? The call will happen on almost every change in .git in all repositories. If you need to call it only for new repositories, just store a list of GitRepositories and c...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Ensure initialization of GitRepositoryManager before doing plugin operation

• 0 votes

Created October 21, 2017 16:31

I think the right thing to do is to subscribe to GitRepository.GIT_REPO_CHANGE events. After all, the toolwindow should be updated, if the user adds a new Git root to the project, or removes one, s...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Ensure initialization of GitRepositoryManager before doing plugin operation

• 0 votes

Created October 21, 2017 16:28

And plain roots as VirtualFiles are not enough, because you need to access GitRemotes, right?

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Ensure initialization of GitRepositoryManager before doing plugin operation

• 0 votes

Edited October 21, 2017 16:08

And when/where do you need this list? Is it a toolwindow that need to show some information about them, or something like that? Because if it is (just for example) something like AnAction which sho...

1. Community
2. IntelliJ IDEA Open API and Plugin Development
3. Ensure initialization of GitRepositoryManager before doing plugin operation

• 0 votes