-
-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
the jekyll-last-modified-at plugin doesn't work correctly #40
Comments
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~ |
Restore the modification time (mtime) of all files in work tree, based on the date of the most recent commit that modified the file.
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 |
@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. |
The plugin jekyll-last-modified-at use git-log or file
mtime
to showlast_modified_date_at
date in pages which is pretty awesome.But I found if I use this Action, all of the files git-log would become the last build time.
Is is possible to use jekyll-last-modified-at by this Action?
The text was updated successfully, but these errors were encountered: