When I run git status on a clean branch, I get a message saying there are no changes.

When I run gitree -m, there is no output. This is a bit confusing, because I'm not sure if the command ran successfully or not.

(By the way, really cool package! It really helps me)

Hi I love this, was just wondering if it's meant to show colours for directories and such? Mine just come out grey, but your picture looks like they're blue and bold? Modified ones do go yellow so I'm not sure what's up

There is an error with this repository's Renovate configuration that needs to be fixed. As a precaution, Renovate will stop PRs until it is resolved.

Error type: Cannot find preset's package (github>whitesource/merge-confidence:beta)

I love this script, thank you.

I often have a directory containing stuff I need, but usually not super important when looking what's up, how could quickly filter those.

gt --filter a b c

Would be absolutely amazing and useful.

PS: Oh..., I'm #13. Like #13 is every solved.

We could do this whole thing better using only Git.

Grab a list of all commited/changed/w/e files:

git ls-files --exclude-standard --directory --no-empty-directory -s | awk -F"\t" '{print $2}'

Switch that list option out for -o and drop the awk to list all untracked files.

That way we get everything directly related to Git and can still build a tree as we have the full paths.

Hello,

First of all, gitree is a pretty neat tool!

##I have a feature request.
It could be nice to group folders together and then files in the output.

Lets have an exemple:

└── api
    ├── assets
    │   └── img
    ├── index.js
    ├── package-lock.json
    ├── package.json
    └── twig
        ├── _layouts
        │   └── default.twig
        ├── index.twig
        └── partials
            ├── header.twig
            └── socials.twig

What if folders were at the top ?

└── api
    ├── assets
    │   └── img
    └── twig
    │   ├── _layouts
    │   │   └── default.twig
    │   └── partials
    │   │   ├── header.twig
    │   │   └── socials.twig
    │   └── index.twig
    ├── index.js
    ├── package-lock.json
    └── package.json

Does it make sense ?
Am I the only one looking for this kind of output ?

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Datasource	Name	Replacement PR?
npm	eslint-plugin-node
npm	eslint-plugin-standard

Pending Approval

These branches will be created by Renovate only once you click their checkbox below.

• Replace dependency eslint-plugin-node with eslint-plugin-n 14.0.0
• Update actions/checkout action to v4
• Update actions/setup-node action to v4
• Update dependency chalk to v5
• Update dependency commander to v12
• Update dependency eslint to v9
• Update dependency eslint-plugin-promise to v7
• Update dependency execa to v9
• Update dependency ignore to v6
• 🔐 Create all pending approval PRs at once 🔐

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update all non-major dependencies (chalk, eslint, eslint-plugin-import, execa, ignore)

Detected dependencies

• Check this box to trigger a request for Renovate to run again on this repository

Running gitree -m inside a folder in a Git repository will still list all files from the repository's root.

In the spirit of ls -l

The main file attributes of concern for git that are not visible in gitree currently are file size and permissions.

An alternative might be to colour executable files differently, in the same way, since this is the main permission that matters.

It would also be nice to have a -c flag to show the most recent commit that a file was changed in, with some date and author information.

Assigning a target that defaults to ./ would be cool.

The -m flag does nothing now.

It's passed to the looper utility, but it doesn't make use of it.

The idea was that we'd use it to stop files logging from there, but the best we can do without a larger change is to log all folders and changed files. That's because stuff gets logged as it comes in, so the folders don't know they're empty as they'll never be listed in git ls-files. Joy, eh?

Will figure this out some point soon. The slight reformat is for the best, just need a happy way to sort this out.

Files listed inside a directory are returned relatively to the current directory whilst the statuses are given as relative to the Git root directory.

This mismatch means that running gitree inside a directory within a Git repository shows no (or possibly incorrect) status information.

We'll need to somehow parse everything as relative to the Git root when we figure out statuses etc, but then clip parts of the path before we build a tree.

It would be nice to be able set the default options.

For now I've created a git alias

zsh:

git config --global alias.tree "\!gitree -m -c"

./git/config file:

[alias]
	tree = "!gitree -m -c"

Usage:

Whack that header in and paste a print-out of the tool's help log.

Sorted.

tree has the -L option that allows depth limiting of the tree. This would be super useful in gitree too. Happy to make a PR if it would be appreciated.

git ls-files doesn't show staged deleted files.

git status --porcelain -z -uall still lists it, however. Is there a nice way we can leverage that to still include it in the listings?

This change may go hand-in-hand with reformatting the statuses so that we assign x, y, from and to to all files before we start looping over them to log 'em.