Repository navigation
Avoid keeping commit history on gh pages branch #46
Description
Hallo!
I have a question, is it possible to deploy on gh pages and avoid keeping the commit history with your package?
For example, Travis CI has the option keep-history when deploying on gh pages to configure this behavior and its default is false.
If you want to know my opinion is a good feature, because people usually don't want to keep track of their github pages deployment, that is just an environment to be able to serve your files, even they are almost not human readable if you are using webpack based projects .
I have an Angular project and if you see its gh-pages branch doesn't give any useful information
Activity
JohannesHoppe commentedon Dec 2, 2018
That's a great idea. We should add this feature one day. I usually push to a separate repo, this keeps the code-repo clean and I still have an archive of all builds.
[-]Avoid keep commit history on gh pages branch[/-][+]Avoid keeping commit history on gh pages branch[/+]JohannesHoppe commentedon Dec 23, 2019
Found this open PR:
tschaub/gh-pages#277
JohannesHoppe commentedon Jan 6, 2020
see #90, this can be only implemented if we fork gh-pages
JohannesHoppe commentedon Jan 12, 2026
Closing this issue as it's been open for quite a while without activity. A lot has changed since 2019 – we've released v3.0.0 with major updates!
If this is still relevant, feel free to open a new issue with fresh context. Thanks for your contribution! 🙏