Allow templating in output flag

[secustor]

Thanks for this very useful piece of code. It has been very helpful.

I'm using it to gather data from multiple repos and then concat the result using the print sub command.
The problem is that the resulting file is getting too big for efficient processing

A solution would be to allow templating in the output flag that way such a use case would be possible:

multi-gitter print report.sh -o myorg --output "./results/{{ .REPOSITORY }}.json"

Glancing at the code base this should be doable by moving the creation of the output stream to

multi-gitter/internal/multigitter/print.go

Line 61 in 12c0422

func (r Printer) runSingleRepo(ctx context.Context, repo scm.Repository) error {

If you don't see blockers, I will look into implementing it.

[lindell]

I think the same thing could be archived adding the repo name by using $REPOSITORY and piping the output through a script that is splitting it. But I would absolutely accept a PR if you want to implement this within multi-gitter ☺️

[lindell]

This is specifically what I'm thinking about, since it seems that you output json, let's use that in the example.

split.sh:

#!/bin/bash

while read line
do
    repo=`echo $line | jq -r .repo` # Get the name of the repository from the top level json
    mkdir -p -- "${repo%/*}" # Make sure the folder exist
    echo $line >> $repo # Add to the file
done < /dev/stdin

And test-script.sh:

#!/bin/bash

echo "{\"repo\":\"$REPOSITORY\"}" # This is ofc more advanced in reality 

Then run with:

multi-gitter print ./test-script.sh -O my-cool-org | ./test.sh

Result:

[secustor]

Thanks, for the example code!

But I have started implementing this in code anyway, because it simplifying the scripting which would be necessary.

It works, but I have still some regression. If I have fixed it up, I will provide a PR.