Add status command

[Reinmar]

Should pretty-print the statuses of all repos.

We need to figure out which information are the most important and a nice way to print them (some sort of a table?).

[Reinmar]

I'm missing this command quite badly. I'm using mgit exec 'git st' but it's hard to read when you have 20 repos.

I'd like this command to print a table with the following info:

1. package name,
2. branch name || detached,
3. hash,
4. short status about changes – modified files, files added to the indes, new files,
5. info: ahead/behind/on branch.

How nodeprompt does it is really good. All important information is present and proper colors are used to make it even easier to read.

[oleq]

These are the command that I use when working with branch constellations:

mgit exec 'git status | grep "not staged" && git st'

mgit exec 'git status | grep "not staged" && git diff'

mgit exec 'git status | grep "On branch t/" && echo $PWD'

[Reinmar]

I wonder which of these we could:

• include in mgit st options,
• for which we could've some configurable shortcuts in mgit exec,
• and which deserve their new commands.

I'd say that:

1.

mgit exec 'git status | grep "not staged" && git st'

Could become:

• mgit st --modified – prints a table only repos with any changes (includes not staged and untracked files) .
• mgit st --details – prints a table but with a column called "Details" that would contain a list of untracked and modified files.

2.

mgit exec 'git status | grep "not staged" && git diff'

Could become mgit diff.

The --modified command is not needed here because by default we should only print repos where there were any changes.

The important thing here is that we should not lose colors. AFAIK the way we execute commands on multiple repos now means that we lose the colors and we'd need to completely change that bit of the code. Since this method proved to be really stable, I wouldn't like that. So, if there's no other option, that command would need to work like this:

1. retrieve statuses of all repos using the concurrent command execution,
2. check which changed and get diffs for only this repo without involving concurrency.

After all, usually you'll have any changes in just a few repos.

However, I'd really check if we can't preserve colors without changing the execution method.

3.

mgit exec 'git status | grep "On branch t/" && echo $PWD'

This will be really well visible in mgit st. Repos which are not on master or major could be marked in some way – maybe slightly highlighted?

@oleq, WDYT?

[pomek]

Status of the mgit status command:

The status command is available as st.

A pink row means – branch in the package is other than defined in mgit.json. Other symbols are explained in the Legend.

Thanks @oleq for help to polish the table.

[pomek]

Status of the mgit diff command:

• For diff command we don't display the counter in repository bar:

• By default we display changes (not staged) from all repositories:

• But we can restrict the scope (already available):

• even more:

• We can pass options directly to the diff command:

• These options can be defined even if some options for mgit was set:

• When there are no changes, nothing will be displayed:

• but if we add changes to staged…

So basically, we can use mgit diff as an alias of mgit exec 'git diff' what was the main goal for this command.

[pomek]

After all, I executed mgit st which prints:

[Reinmar]

Wow, amazing work on these commands. I really like every bit of them. Great job!