You could give this a try. My guess is that from the GUI you could
hook into Git | Push... action and maybe make it as simple as add a
'Gerrit' checkbox which changes the upstream you push into.
Or you could just implement the backend and read the git config
properly then do the right thing and pe
:-)
Despite being in the US for 40 years, I swear English is my 2nd language
:-) When I used 'we', I meant we were using git and 'I' was using NB's git
plugin (point being we weren't using code review). Sorry.
tom
On Thu, Jan 2, 2020 at 5:09 PM Emilian Bold wrote:
> Oh, I didn't realise you ar
Oh, I didn't realise you are using the royal 'we'. I assumed the whole
team is on NB (although, fully expecting not the whole company).
1 out of 2000 seems pretty low though. Are you sure there aren't more
NB refugees hiding somewhere? Opening the Profiler when no colleague
is looking.
--emi
On
...except that nobody in my company (some 2,000 devs), aside from me, uses
Netbeans and the IDEs that are used (IntelliJ, Eclipse) do have hooks into
gerrit. So they may not be convinced by your calculations :-(
Anyway - thanks for the feedback.
Tom
On Thu, Jan 2, 2020 at 4:48 PM Emilian Bold w
It's not the answer you are looking for but this would be a perfect
moment for your company to either develop or pay for this:
5 team members * 2 commits / day * 5 days / week * 4 weeks * 2 minutes
lost per commit made outside the IDE = 400 minutes / month = 6.5
billable hours wasted every month.
We've been happily using git from within NB for a few years. Now corporate
insists we use gerrit for code review. It seems like NB doesn't have
support for pushing changes for review to gerrit - the only suggestion of a
hack solution I saw was from 2015 in this stack overflow question:
https://st
