Version 5.7.0 of tslint just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As tslint is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

This extension does not work when running VSCode through the browser via Code Server while hosted entirely on a separate server.

Expected (upon starting vscode-ungit):

• Ungit starts running on the external server.
• VSCode opens a new tab with Ungit.

Actual Results:

• Ungit starts running on the local device, if possible. (Incorrect)
• Ungit does not start running on the server.
• VSCode opens a new tab and points to a local instance of Ungit at localhost:8448, regardless of availability.
• If Ungit was not able to start (not installed/no access to terminal) window shows "Localhost refused to connect".

Proposed solution:
Ungit provides a method for setting a urlBase other than localhost from the command line, shown in config.js.

If this can be set from .vscode/package.json and propagated throughout vscode-ungit to start/request visuals from Ungit on the correct machine, it may be all that's needed.

Figured I'd throw this out there in case the dev/someone who's closer to this project is able to approach it faster than I can as I acquaint myself with TS.

Below: Reference to the hardcoded localhost.

When I start ungit from vscode, the extension works correctly, but after few commits (a dozen) the application becomes more and more slow and finished to crash and restart

The devDependency @types/node was updated from 10.12.8 to 10.12.9.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Ungit was my favorite git GUI. But now it's gone. :-( I suspect I first became acquainted with it while using Brackets. Eventually, I started using it with VS code. Regardless, it no longer seems to be working in either. This is what I get when I try launching it in VS code:

The window runs indefinitely. The behavior in Brackets is similar. Since I'm not getting any errors, I don't know how to proceed.

So, I decided to try running it from the commandline…

Perhaps I need to include a command-line option to use it this way.

is there a way to prevent this? It can get quite slow if I have changed a lot of files because every time ungit has to build the change diff again.
Also my commit message gets lost.

Hi,

I really like ungit and making it work from VSCode would be a godsent.

Could you please check why it stays in "Starting Ungit" forever?

Thanks!

🚨 You need to enable Continuous Integration on all branches of this repository. 🚨

To enable Greenkeeper, you need to make sure that a commit status is reported on all branches. This is required by Greenkeeper because we are using your CI build statuses to figure out when to notify you about breaking changes.

Since we did not receive a CI status on the greenkeeper/initial branch, we assume that you still need to configure it.

If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with greenkeeper/.

We recommend using Travis CI, but Greenkeeper will work with every other CI service as well.

Since the upgrade to VSCode version 1.36, it seems there is an issue when I try to fill the title commit message. The cursor blink on the left panel and also on the ungit title field and when I try to write something, it writes only on the left panel. If I click on the ungit tab or if I close the left panel I don't see the cursor and I can't write.

Any idea ?

When ungit command issued but ungit server has been started by another process the 'Loading...' screen stays on forever.
You need to manually kill ungit server for the plugin to resume correct operation.
It is not necessary that this happens as you can attach to the existing ungit server.

may it be optimized that Ungit graphs display too large in splited views as:

@capaj, would you be interested in helping test a feature to use a global ungit installation with the extension?
Branch: https://github.com/Hirse/vscode-ungit/tree/feature/global-ungit
Archive: vscode-ungit-1.0.1.zip

After installation, if I try to start ungit, it get the error:

Error: command 'extension.ungit' not found

Vscode: 1.13.1 (Ubuntu)

The devDependency vscode was updated from 1.1.30 to 1.1.31.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

vscode is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

This banner is too annoying (as is the help-improve banner), especially as it's repeated every time the window repaints

"A new version of ungit (1.2.2) is available! Run npm update -g ungit to install. See what's new in the changelog"

Hello, when I want to open the extension, it waits forever.
I do not know if I'm doing something wrong or something is happening.
Please tell me what may be happening.

Video ▶ http://recordit.co/xG48DhXnYS

Context

• macOS 10.12.6
• VSCode 1.18.0
• vscode-ungit extension 1.1.1
• Ungit 1.2.3

Description

When opening an ungit tab on VSCode, shortly after the focus is set on the default web browser where a new tab is opened to the address http://localhost:8448/#/repository?path=%2F, which points to the filesystem root (which for obvious reasons is not a git repository).

The tab opened in VSCode is correctly pointing to the workspace root.

I got this warning today:

"Extension 'Hirse.vscode-ungit' uses the 'vscode.previewHtml' command which is deprecated and will be removed soon. Please file an issue against this extension to update to use VS Code's webview API."

VSCode version 1.32.1

On the latest release of VScode (1.62.2) the current Ungit extension (v2.2.3) doesn't start - it stays at the loading prompt indefinitely

I'm not sure if there were changes to extensions in the latest release but this is still working on the previous release of VScode

every time ungit is open, it will be displayed in a new view.

Is it possible to display it in the current view?

Using the Remote - SSH extension and ssh-add to forward my key to the remote server I get the following "Unhandled git error":

[email protected]: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.

I can access BitBucket from the command line:

$ ssh -T [email protected]
logged in as xxx
You can use git or hg to connect to Bitbucket. Shell access is disabled

I'm using the following .ssh/config to forward the ssh agent and port for ungit:

...
ForwardAgent yes
LocalForward 127.0.0.1:8448 127.0.0.1:8448
...

Is this something related to the vscode ungit extension or something related to FredrikNoren/ungit?

Version 1.31.0 of vsce just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As vsce is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

There is a variable named git.path in vscode settings that allow to specify the path for the git binary.

For example GlitLens extension also used this variable for determine de git binary path.

Is it possible that ungit also used this variable for determine the git path ?

Hello,

On Linux credentials-helper is not executable and and that cause some problems :

-rw-r--r--. 1 gigix gigix 1,1K  1 juil. 20:39 VSCode/extensions/hirse.vscode-ungit-1.5.0/node_modules/ungit/bin/credentials-helper

Is it possible to set execution on this binary ? on official ungit github repository there is the executable set.

Version 2.5.2 of typescript just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As typescript is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Version 3.5.1 of mocha just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Hi,
I've trouble getting the VSCode plugin for ungit to work - seems that the plugin does not recognize any git repositories. Any idea why? For more information on the issue and the analysis thus far, please see the thread on the original ungit GitHub presence: FredrikNoren/ungit#1402. Appears to be an issue with the plugin rather than ungit itself. Thanks.

Version 2.2.43 of @types/mocha just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As @types/mocha is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

Is this the intended behavior? When I switch to a file and then back to ungit, it reloads. This is different of when changing files on disk, when ungit rechecks the repository. When I say reload I mean load the entire repository, etc (tab is initially blank). This causes to be heavier without the need to.

Hello,

Is is possible to add a button to start ungit in the right top corner of VSCode ? (with the possibility to hide or show this button in the configuration like "ungit.showButton": true).

Regards

Version 8.0.26 of @types/node just got published.

This version is covered by your current version range and after updating it in your project the build failed.

As @types/node is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Your Greenkeeper Bot 🌴

I just want to know if it is possible to prevent the ungit view from opening in split view.
Thanks