Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

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

See original GitHub issue

🐛 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

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

Issue Analytics

State:
Created 3 years ago
Comments:6 (1 by maintainers)

Top GitHub Comments

1reaction

slorbercommented, Jun 23, 2020

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

1reaction

slorbercommented, Jun 17, 2020

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.