-
Notifications
You must be signed in to change notification settings - Fork 26
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
Check commit messages for specific fragments and/or length #68
Comments
Currently working on this issue to check if commit messages meet a length requirement. |
Hello @baldeosinghm can you please update as to whether or not you finished working on a PR that resolves this issue? Your note is the last one in the issue tracker and thus I wanted to check with you today! Thanks for any updates that you can share! |
I wanted to write that I plan to implement this feature in the next few days. @quigley-c and @baldeosinghm if you would like to review the PR for this work, please let me know. Thanks! |
I plan to work on this issue after implementing the new "linting-style" interface to GatorGrader. |
@Michionlion I have put this issue on hold until after we implement the linting interface. My view is that, currently, adding this feature would require me to change the command-line interface, which I would prefer not to do and then have to change once we implement the linting approach. |
The current implementation of GatorGrader can only count the number of commits in a repository past a certain number. However, it would also be useful if the tool could look for fragments inside of a commit message. For instance, one idea would be that students must add a numerical rating for their level of frustration associated with that commit. Alternatively, GatorGrader could check to see if the commit messages contain an emoji in them (perhaps from a set list of emoji). Finally, it might be a good idea to introduce checks that can ensure that commit messages have a minimum or a maximum number of characters in them. Of course, if we introduce this type of feature, then we would also have to explain to students how to revise their commit messages so that they meet the standard that we are asking them to follow.
The text was updated successfully, but these errors were encountered: