-
Notifications
You must be signed in to change notification settings - Fork 27
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
Invalid DateTime in the Commit Message #83
Comments
Could you share what values you're using for the timeline and message format settings? I'd just love to be able to try and repro this myself. |
Hello Jonathan,
Thank you for your reply.
My commit message format is ff (I believe that's the default one)
[image: image.png]
Regarding the timeline question , I am not sure what parameter you are
referring to.
Can you please clarify for me where is this timeline parameter specified?
Regards,
…On Thu, Dec 26, 2024 at 6:51 PM Jonathan Carter ***@***.***> wrote:
Could you share what values you're using for the timeline and message
format settings? I'd just love to be able to try and repro this myself.
—
Reply to this email directly, view it on GitHub
<#83 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADT6XJKTE6XPYW6AUJK5YS32HQ62VAVCNFSM6AAAAABQHIWJVSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRSHE4DOMBTGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Oh sorry, I meant the time zone setting. |
My Time Zone setting is FR |
By The Way, is there a way to hard code (predefine) a Commit Message ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello there,
Just discovered GitDoc and I like it very much!
Everything works as expected , for me, apart from this small glitch:
Regardless of my settings inputs for TimeZone and Commit Message Format (including the default ones) , I always end up with a commit message "Invalid DateTime" in my Git repository (self hosted Gitea)
The text was updated successfully, but these errors were encountered: