tomasbonco / gitlabtree Goto Github PK

I know you can run a self-hosted instance of GitLab but having a GitLab specific add-on active on all pages seems scary

First of all, nice extension. Relaxed my mind while checking MR's.

I guess it's pretty unnecessary if I have changes only 1 file, since it's path is clearly shown on the top of the diff block.

1. Changed files list contains a hidden element with inline style instead of .hidden class.
2. Width is not adjusted according to window width.
3. Every time a changed file is selected, the window scrolls a bit upwards.

In some (ehm, Java) languages, it is common to have code separated by packages that are a fairly deep folder structure, often in the form of com.github.janecekpetr.projectname.packagename...

This is what happens then: https://i.imgur.com/u2BOlmV.png (sorry for lots of blur, this is my work's code)

I'm asking for collapsing the whole main/java/com/.../.../util structure (all folders containing no changes, just another folder) under a single node so that it does not take so much vertical space, and does not indent the actual filenames so much (preserving the horizontal space as well).

Firstly this plugin is a must have for any Gitlab user coming from Bitbucket! Amazing work.

In Gitlab 11.1.4-ee when a user has selected "Layout width" Fluid, extension causes changes to still appear limited.

Looks like in 11.1.4 the limiting CSS is applied in a higher parent. Regardless of setting the changes html still appears like:

<div>
    <div class="diffs tab-pane active" id="diffs">
        ...
    </div>
</div>

It appears this extension is adding:

<div class="container-fluid container-limited limit-container-width">
    <div class="diffs tab-pane active" id="diffs">
        ...
    </div>
</div>

Simply removing the class="container-fluid container-limited limit-container-width" appears to respect the Gitlab user setting.

It would be really great and improve usability if scrolling to top after switching files.

GitLab Community Edition 11.4.5， Not Work。

I have stared using gitlab and i find this extension's purpose useful. I coldn't find this feature in gitlab's current version. Could you guide me towards it.

This Plugins does not work anymore with Firefox 57 and Gitlab-CE 10.3.2

Love this extension already, making migrating from Bitbucket a lot easier. Would love to able to adjust the width of the tree menu. It wouldn't even need to be dynamically resize-able necessarily, just an option in the Chrome extension menu to set the width of the box would be great.

You might want to consider adding an option to toggle the tree mode on or off.

Great tool, by the way.

Last week Gitlab made some modifications to the file list.

The extension broke?

Hi @tomasbonco, thank you so much for this awesome extension.

I only can see the Source Tree on commits. That would be nice to use in any source/file navigating inside the Repository/Files similar what octotree does.

Thanks

Hello 👋

Is there any chance that this plug in can get Safari support ?

Thanks in advance.

Google Chrome version: 70.0.3538.67 (Official Build) (64-bit)
GitLabTree version: 1.0.1

While scrolling vertically in the merge view the gitlab tree shall remain visible. Currently it does not so switching to new files implying scroll vertically to top of the window.

Not that big of an issue, but once the Changes tab is opened, if we visit any other tab, it widens the tab content for every other tab too, which is a bit weird

My organization uses a self-hosted Gitlab that is currently using [email protected]. We have plans to move forward to 11.x soon, but it's still a ways out.

I imagine now that GitLab 11.x has a similar feature this plugin could/would change considerably by building off of existing functionality from 11.x.

In the interest of supporting a larger audience, what would it take to support, say, GitLab's latest two major versions?

Thoughts?

It will be nice to have some hotkeys for navigating to next/previous file. Of course, such hotkeys shall be active only when the tree is active.

We use Gitlab Enterprise ver 11, and after I install this extension, nothing happens.

I don't see anything that looks like the picture, and there isn't any setup document anywhere.

So, do I need any extra steps to make it works? Or it just simply incompatible with Gitlab version 11?