The benchmark data is deleted after every doc publish

[Manan17]

🐛 Describe the bug

Due to the new change in the gh-pages branch, the benchmark data got lost as it deletes everything and creates a new doc after every commit is merged. Initially I had set it to false, so it wouldn't run and the data will be preserved. This commit changed it: https://github.com/linkedin/Liger-Kernel/pull/867/files
So now there is no active link (ie. https://linkedin.github.io/Liger-Kernel/benchmarks) as it used to be for displaying the benchmarking results.

cc: @shimizust @vaibhavjindal @ParagEkbote

Reproduce

No response

Versions

Liger: 0.6.2

[ParagEkbote]

Well, previously the gh-pages branch were not being updated at all after each change to the docs.

So,now the docs are now not completely up to date as compared to the readme. We could create a separate benchmarks.md to maintain the benchmarks. WDYT?

[Manan17]

The benchmark data structure was something like benchmark/commit_hash/benchmark.csv file contain all the data. You can have a look over here: #746.
So the web page gets the data from the gh-pages branch. We need to figure out how would we keep the benchmark data as it is or find a way to store in on some other branch and display it.
Btw, do you know if we can get back the previous data that we stored? Like can we get it from commit history or no?

[shimizust]

The benchmark commits are still visible on the upstream:

git log --oneline upstream/gh-pages --grep="benchmark"
77d5fc0 (HEAD, upstream/gh-pages) Add benchmark for commit 77a4c1a-v0.6.2
e5ef3c9 Add benchmark for commit 77a4c1a
67e782d Add benchmark for commit 90d66ce
4325178 Add benchmark for commit 65c0ad1
1aa6252 Fixing URL issues (#849)
19b295f Add benchmark for commit 2845fe8
6f1ffbb Add benchmark for commit
e27da7c Add benchmark for commit 5e8f12b
9610d97 Add benchmark for commit 02bac05
d70a26b Add benchmark for commit 08906d3
6aeb1f8 Add benchmark for commit d47751c
fabf99f Revamping the UI and flow of the webpage. (#771)
e0d0c11 Add benchmark for commit 0701bab
5309ba6 Add benchmark for commit c1bdc24
b9bc0a5 UI for the benchmarking results (#529 

So the issue is with the force deploy which overwrites the entire history? Are we able to do do mkdocs gh-deploy --clean instead to preserve benchmark commits and the updated docs pages?

      - run: mkdocs gh-deploy --force

[shimizust]

@vaibhavjindal can you help with this?

[vaibhavjindal]

@vaibhavjindal can you help with this?

Sure, will take a look