We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Improvement
High
Following issue #549, using interrogate is a powerful way to make sure our docstrings are completed.
Integrating this with CI will ensure we don't miss any docstrings going forward.
CI runs interrogate on all changed files in a PR.
No response
The text was updated successfully, but these errors were encountered:
@dagardner-nv Setting this to 23.03, if you somehow find a moment in 23.01 feel free to change.
Sorry, something went wrong.
Closed by #628
dagardner-nv
No branches or pull requests
Is this a new feature, an improvement, or a change to existing functionality?
Improvement
How would you describe the priority of this feature request
High
Please provide a clear description of problem this feature solves
Following issue #549, using interrogate is a powerful way to make sure our docstrings are completed.
Integrating this with CI will ensure we don't miss any docstrings going forward.
Describe your ideal solution
CI runs interrogate on all changed files in a PR.
Describe any alternatives you have considered
No response
Additional context
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: