[
https://issues.apache.org/jira/browse/HADOOP-19193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17852351#comment-17852351
]
ASF GitHub Bot commented on HADOOP-19193:
-----------------------------------------
pan3793 opened a new pull request, #6864:
URL: https://github.com/apache/hadoop/pull/6864
### Description of PR
Currently, the gh-pages deployment always creates new commits based on the
previous one, which causes the git repo size to grow fast.
According to
https://github.com/peaceiris/actions-gh-pages?tab=readme-ov-file#%EF%B8%8F-force-orphan-force_orphan,
we can use `force_orphan: true` to create an orphan commit which is sufficient
for website deployment cases, as it is some kinds of compilation outputs, we
don't need to need to keep all history commits.
### How was this patch tested?
Review.
### For code changes:
- [x] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
> Create orphan commit for website deployment
> -------------------------------------------
>
> Key: HADOOP-19193
> URL: https://issues.apache.org/jira/browse/HADOOP-19193
> Project: Hadoop Common
> Issue Type: Improvement
> Components: documentation
> Reporter: Cheng Pan
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
