-
-
Notifications
You must be signed in to change notification settings - Fork 906
fix: corrected spacing in if condition in geometric quantile implementation #5948
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
fix: corrected spacing in if condition in geometric quantile implementation #5948
Conversation
--- type: pre_commit_static_analysis_report description: Results of running static analysis checks when committing changes. report: - task: lint_filenames status: passed - task: lint_editorconfig status: passed - task: lint_markdown status: na - task: lint_package_json status: na - task: lint_repl_help status: na - task: lint_javascript_src status: na - task: lint_javascript_cli status: na - task: lint_javascript_examples status: na - task: lint_javascript_tests status: na - task: lint_javascript_benchmarks status: na - task: lint_python status: na - task: lint_r status: na - task: lint_c_src status: missing_dependencies - task: lint_c_examples status: na - task: lint_c_benchmarks status: na - task: lint_c_tests_fixtures status: na - task: lint_shell status: na - task: lint_typescript_declarations status: na - task: lint_typescript_tests status: na - task: lint_license_headers status: passed ---
Hello! Thank you for your contribution to stdlib. We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:
This acknowledgment confirms that you've read the guidelines, which include:
We can't review or accept contributions without this acknowledgment. Thank you for your understanding and cooperation. We look forward to reviewing your contribution! |
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.
👋 Hi there! 👋
And thank you for opening your first pull request! We will review it shortly. 🏃 💨
Coverage Report
The above coverage report was generated for the changes in this PR. |
lib/node_modules/@stdlib/stats/base/dists/geometric/quantile/src/main.c
Outdated
Show resolved
Hide resolved
…rc/main.c Signed-off-by: Gunj Joshi <[email protected]>
Thanks @mukulchauuhan! |
@mukulchauuhan Is there an issue that this PR is intended to close? |
Yes it was issue #5948 |
@kgryte Sir, |
Thanks for the clarification! I’ve added Closes #5948 in the PR description to link the issue properly. Let me know if there’s anything I should improve. |
@mukulchauuhan #5948 is this PR, so that cannot be the issue this PR is resolving. |
@mukulchauuhan You have inserted your own template for the initial PR comment, you can still edit the comment and use the native template for pr requests. The default template gives a lot of clarity. Refer the introductory markdown files before you proceed. |
Thank you for the valuable feedback, @anxhukumar |
Hello! Thank you for your contribution to stdlib. We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:
This acknowledgment confirms that you've read the guidelines, which include:
We can't review or accept contributions without this acknowledgment. Thank you for your understanding and cooperation. We look forward to reviewing your contribution! |
1 similar comment
Hello! Thank you for your contribution to stdlib. We noticed that the contributing guidelines acknowledgment is missing from your pull request. Here's what you need to do:
This acknowledgment confirms that you've read the guidelines, which include:
We can't review or accept contributions without this acknowledgment. Thank you for your understanding and cooperation. We look forward to reviewing your contribution! |
@mukulchauuhan #5948 is not the issue you are solving, that represents your pr. Use a correct issue tag. |
Hi @anxhukumar, I wanted to double-check something. I believe this pull request is intended to address issue #5948 (the geometric quantile implementation spacing issue). Could you help me understand what you're seeing that suggests a different issue? I'm still learning the process, so any guidance is appreciated! When I'm writing Resolves 5948, I think this means this is connected to the issue number and not the pull request number. If this is the case then I am putting the right thing on the top, i.e. resolves 5948 which is indeed the issue number for the related issue fix: corrected spacing in if condition in geometric quantile implementation #5948 I didn't clearly get this thing that you said about - Use a correct issue tag ! Please can you provide me more information regarding my mistake (if I am making any) :) |
@mukulchauuhan In order for this PR to move forward, we need to know the issue number that this PR is intended to resolve. Please find the issue number from the following list of issues: https://github.com/stdlib-js/stdlib/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen |
@kgryte, Hello Sir, I had been searching this issue for more than an hour, I think I am loosing something. Either I am unable to see the issue there or it is not present. But I remember it was present and had a good first issue tag on it. Please help me out sir. |
Resolves #5948
Description
This pull request:
if
condition of the geometric quantile implementation.Related Issues
This pull request:
Questions
No.
Other
No additional notes.
Checklist
@stdlib-js/reviewers