Skip to content
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

[FEA]: Enable 'interrogate' as part of CI #622

Closed
2 tasks done
jarmak-nv opened this issue Jan 23, 2023 · 2 comments
Closed
2 tasks done

[FEA]: Enable 'interrogate' as part of CI #622

jarmak-nv opened this issue Jan 23, 2023 · 2 comments
Assignees
Labels
feature request New feature or request

Comments

@jarmak-nv
Copy link
Contributor

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

  • I agree to follow this project's Code of Conduct
  • I have searched the open feature requests and have found no duplicates for this feature request
@jarmak-nv jarmak-nv added the feature request New feature or request label Jan 23, 2023
@jarmak-nv
Copy link
Contributor Author

@dagardner-nv Setting this to 23.03, if you somehow find a moment in 23.01 feel free to change.

@mdemoret-nv
Copy link
Contributor

Closed by #628

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request New feature or request
Projects
Status: Done
Development

No branches or pull requests

3 participants