Releases: GatorEducator/gatorgrader
v0.3.1
Improve the documentation in the README file.
The current documentation contains small mistakes.
This PR fixes those small mistakes, clarifying the purpose of the tool and its comparison to other tools.
- Commit messages that are correctly formatted
This PR is a small change that fixes #89, fixes #92, fixes #101, fixes #131, and fixes #139.
Note that this PR only makes changes to the README file.
Auto-generated by pr-tag-release
v0.3.0
Support Wildcards in File Fragment Checking
Currently you can specify a filename, but not a wildcard.
You can specify a wildcard, like *.py when looking for fragment.
- Commit messages that are correctly formatted
- Tests for newly introduced code
- Docstrings for newly introduced code
This PR is a feature that fixes #98.
Auto-generated by pr-tag-release
v0.2.7
Use Radon/Xenon for Code Maintainability Diagnostics/Checking
This PR uses radon for the display of diagnostics about code maintainability. It also uses xenon to run the same maintainability checks, but to fail the build if aspects of the project fall below a specific threshold. The PR contains integration into the lint.sh and lint.bat files which are integrated with Pipenv.
What is the current behavior?
The maintainability of the source code is not calculated or checked.
What is the new behavior if this PR is merged?
The maintainability of the source code will be both calculated and checked.
Other information
This PR has:
- Commit messages that are correctly formatted
This PR is a small change.
Developers
Auto-generated by pr-tag-release
v0.2.6
Create a Template for Git Commit Messages
This PR provides a template for Git commit messages.
What is the current behavior?
Someone can type a commit message in their own format.
We only ask them to change the message if it is really bad.
What is the new behavior if this PR is merged?
This will make the commit messages more consistent. I'm open to different
formats for the commit message, but picked this one after reading some articles.
I will try it and adjust it as needed. What would you prefer?
This PR has:
- Commit messages that are correctly formatted
This PR is a small change.
Developers
Auto-generated by pr-tag-release
v0.2.5
Add Correct Support for File Name Case Across Operating Systems
This pull request fixes the feature that checks for the existence of a file. It includes test cases that establish a confidence in the correctness of the fix for this feature.
What is the current behavior?
Currently, the outcome of a check depends on the operating system on which you run the check. This means that if a check is run on Windows or MacOS, the checks for the existence of a file will be case-insensitive. However, if a check is run on Linux, then it will be case-sensitive.
What is the new behavior if this PR is merged?
Once this PR is merged, the checks will always run in a case-sensitive fashion. This means that if a check would not pass on Linux it will also now not pass on Windows or MacOS. One way to tell that this is, in fact, the case is by checking the builds on Travis CI for MacOS and on AppVeyor for Windows.
This PR has:
- Commit messages that are correctly formatted
- Tests for newly introduced code
- Docstrings for newly introduced code
This PR is a small change that fixes handling of file names.
Developers
Auto-generated by pr-tag-release