Closed fbiville closed 4 years ago
One solution would be to serialize both the JSON configuration and the license header text in .headache-run
so there is no need to dive into the Git history to get those elements next time headache
runs. That way, headache
would still work fine with shallow clones.
And that would probably fix https://github.com/fbiville/headache/issues/55 as a nice bonus effect!
headache
currently needs to track two pieces of data:.headache-run
was committed along with the source file changes)configuration:/path/to/headache.json
entry in theheadache-run
) that allowsheadache
in a subsequent run to read the former configuration and headerThe downside of this is that
headache
may not work with shallow clones as it requires access to enough of Git history to be able to read configuration at the revision during whichheadache
last ran.