feat: generate the timestamp of creation and last updated for each doc file (close #258)

[ulivz]

Close #258

[meteorlxy]

When a file is saved without any changes, its mtimeMs will update, but git won't track the change. Will that cause some issue?

[ulivz]

Good point, so there is a discussion which type of time should be provided to user.

[yyx990803]

#258 (comment)

[ulivz]

Updated to git commit time stamp.

[inosik]

What if the project uses some other version control system? Or if the project is in its early stages and not under version control yet?

[meteorlxy]

@inosik That's it!

[ycmjason]

@inosik Interesting thought, I think that's a valid point. Perhaps a fallback to fs would be a nice thing to have.

[meteorlxy]

Yeah, I've ever thought about that but forgot to post to that issue.

If a new file is created, but has not been commited into git repo. Then if you are going to dev or build for test, it may cause some issue.

[ycmjason]

@meteorlxy @inosik
Should we create an issue so that we won't forget about this? 🌵

[yyx990803]

Maybe the last updated feature should be off by default, and mention in docs that you need git to use this feature.

[ycmjason]

@yyx990803 that would be nice, since fs timestamp is not very informational anyways.

[inosik]

Should we create an issue so that we won't forget about this?

See #340.

[ulivz]

@yyx990803 fixed it at #338