Added an option to display additional information about submissions in commit logs and folder names.
Commit header
The prefix for automated commits is now changeable. I made some other changes to commit formatting that serve to reduce redundancy and provide more novel information about each commit while still keeping the automated messages reasonably concise.
Folders
I also made it optional to always put problems into their own repo (so that each submission folder can be in the repo's base directory if desired, while still potentially segregating submissions into per-user repos for collaboration).
Miscellaneous
There are also some small tweaks like adding newlines at the end of submission files - recommended for git, but not added automatically by Leetcode. Some diffs are also caused by my Vim config stripping spaces from the end of lines or adding newlines at the bottoms of code files.
Other
The README yaml example might need updating with a new tag if this is merged. Not sure but didn't want to add a new release/tag myself.
Images:
The screenshot below was generated by this yaml (linked to my fork for testing):
Verbose
Added an option to display additional information about submissions in commit logs and folder names.
Commit header
The prefix for automated commits is now changeable. I made some other changes to commit formatting that serve to reduce redundancy and provide more novel information about each commit while still keeping the automated messages reasonably concise.
Folders
I also made it optional to always put problems into their own repo (so that each submission folder can be in the repo's base directory if desired, while still potentially segregating submissions into per-user repos for collaboration).
Miscellaneous
There are also some small tweaks like adding newlines at the end of submission files - recommended for git, but not added automatically by Leetcode. Some diffs are also caused by my Vim config stripping spaces from the end of lines or adding newlines at the bottoms of code files.
Other
The README yaml example might need updating with a new tag if this is merged. Not sure but didn't want to add a new release/tag myself.
Images:
The screenshot below was generated by this yaml (linked to my fork for testing):
And the last screenshot by this one: