the jekyll-last-modified-at plugin doesn't work correctly about jekyll-deploy-action HOT 4 CLOSED

Hi @wholon

Git doesn't record the last modification date, only the commit/author dates for an all commit, so when the GitHub action pull your repository, the modification date will be the same as the creation date, it's not the same as your local environment, but there is a way to do this, I will try to help settle your issue.

Thanks & Regards

from jekyll-deploy-action.

Hi @wholon

Git doesn't record the last modification date, only the commit/author dates for an all commit, so when the GitHub action pull your repository, the modification date will be the same as the creation date, it's not the same as your local environment, but there is a way to do this, I will try to help settle your issue.

Thanks & Regards

Thank you~

from jekyll-deploy-action.

Hi @wholon

Now this feature has been added, please update your action to the latest version. In addition, the date time isn't as the same as it was, because it will restore the modification time (mtime) of all files in the work tree, based on the date of the most recent commit that modified the file.

Thanks & Regards

from jekyll-deploy-action.

@jeffreytse Hi, the fix for this issue is incorrect. I tried this action but the generated date is still wrong for my blog. I have created a PR to fix this issue.

from jekyll-deploy-action.