-
Notifications
You must be signed in to change notification settings - Fork 261
Template for the issue tracker #1603
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@nanjekyejoannah can you make it slightly closer to sklearn's (here and configuration)?
I like specially the fact that they have a code block where to write the code to reproduce, and the fields "Expected results" and "Actual results" (I may prefer the word "behavior" that you use). The "Describe the bug" is also very meaningful.
I have done some modifications, PTAL |
Codecov Report
@@ Coverage Diff @@
## master #1603 +/- ##
==========================================
+ Coverage 88.52% 90.90% +2.38%
==========================================
Files 104 110 +6
Lines 10263 10594 +331
==========================================
+ Hits 9084 9629 +545
+ Misses 1179 965 -214
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @nanjekyejoannah, it looks great!
I think we should update issues link and merge.
If you're new to Geomstats, consider the following options first: | ||
|
||
- reading the Geomstats documentation: https://geomstats.github.io/ | ||
- searching our existing issue tracker for a similar issue (https://github.com/geomstats/geomstats) to see if |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have updated, thank you, I can now use it in the docs, i guess. |
Thanks @nanjekyejoannah! |
This is a proposed template covering details for a bug report, as discussed in our last call with @LPereira95 but also noted in #1597