Docusaurus: [v2] Author name is always same for all of the pages

[apsdehal]

🐛 Bug Report

Whenever an update is made using GitHub action to the website using yarn build and then deploy to gh pages, the author is always the same for all of the pages.

Have you read the Contributing Guidelines on issues?

Yes

To Reproduce

1. Have a look https://mmf.sh/docs

Expected behavior

Author should be the actual person who last updated the docs

Actual Behavior

The author is same and the person who made the recent commit

(Write what happened. Add screenshots, if applicable.)

Your Environment

Docusaurus version used:2.0.0-alpha.56
Environment name and version (e.g. Chrome 78.0.3904.108, Node.js 10.17.0): Node version: v12.17.0
Operating system and version (desktop or mobile): MacOS 10.14.6 (desktop and mobile both)

Reproducible Demo

(Paste the link to an example repo, including a siteConfig.js, and exact instructions to reproduce the issue.)

https://mmf.sh/docs

Seems somewhat related to #2798

[yangshun]

Agreed. Seems like a GitHub actions thingy. Local deployment should work fine.

[slorber]

afaik Github Pages deployment need to commit to a gh-pages branch to deploy, and we read the github history to know which doc has been updated by which git user last

https://github.com/facebookresearch/mmf/commits/gh-pages

as you can see, reading this history could only lead to the github bot :(

Honestly I'm not fan of using github pages anymore. Options like Netlify are free, much simpler to setup and do not need to commit anything to the repo.

[slorber]

I've opened a doc issue here: https://github.com/facebook/docusaurus/issues/2953

@apsdehal wonder if you could try to host on Netlify or Vercel, and give me feedback on how simple it was compared to Github actions?

[Jason-2020]

See the comment for solution. https://github.com/facebook/docusaurus/issues/2798#issuecomment-636602951
It's not only v2 or Github thing. It's just behaviour of your CI environment.

[slorber]

thanks @Jason-2020

@apsdehal can you tell if this works great for your usecase?

[slorber]

@apsdehal I'm closing as I think @Jason-2020 gave a solution.