fix(v2): read last update from inner git repositories

[felipecrs]

Motivation

My use case:

website/ # a repo
|   external/
|   |  repo-a/ # another repo, ignored by git at website/
|   |  repo-b/ # another repo, also ignored by git

With the current implementation, the lastUpdate won't return any data, as the files are unknown by Git when using website as the cwd. But if we call git in their own folders, git will be able to properly read the metadata.

Have you read the Contributing Guidelines on pull requests?

Yes

Test Plan

I verified by replacing the content of lastUpdate.js in my node_modules folder, which worked. But if needed, I can find a way to record a video. I just didn't record yet because in my tests there are private data from my company.

The good news is that this change won't break any existing use case, it will just fix mine.

Related PRs

None

[netlify]

✔️ [V2]
Built without sensitive environment variables

🔨 Explore the source changes: 08f8e98

🔍 Inspect the deploy log: https://app.netlify.com/sites/docusaurus-2/deploys/60d37c8fba8573000804c2d2

😎 Browse the preview: https://deploy-preview-5048--docusaurus-2.netlify.app

[github-actions]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🟠 Performance	55
🟢 Accessibility	98
🟢 Best practices	100
🟢 SEO	100
🟢 PWA	95

Lighthouse ran on https://deploy-preview-5048--docusaurus-2.netlify.app/

[slorber]

Thanks, that looks fine 👍 as long as it does not break current lastUpdate for simpler setups

[slorber]

Hi @felipecrs

Just wondering, is your site with multiple Git submodules opoen-source?

I'd be interested to check it because we'd like to optimize those git log calls as part of e18e/ecosystem-issues#216 and your setup might be a good representative example to benchmark against

[felipecrs]

Unfortunately it is not. It would otherwise be a good benchmark candidate indeed!

(unless you want me to benchmark for you)