Both of the mentioned features assume that the repository exists in the same directory as the content, which may not be the case.
They both currently appear to be using different modules (pygit2 for test & git for release_notes) so the solution can't quite be a one size fits all approach today.
There should either be a repo_path config option, or both features aligned to use the same module such as pygit2, where something like the following could be used:
Both of the mentioned features assume that the repository exists in the same directory as the content, which may not be the case.
They both currently appear to be using different modules (pygit2 for test & git for release_notes) so the solution can't quite be a one size fits all approach today.
There should either be a repo_path config option, or both features aligned to use the same module such as pygit2, where something like the following could be used: