-
Notifications
You must be signed in to change notification settings - Fork 54
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
Diabetes Classification| Feature Importance #119
Comments
Congratulations, @Anuragsarkar12! 🎉 Thank you for creating your issue. Your contribution is greatly appreciated and we look forward to working with you to resolve the issue. Keep up the great work! We will promptly review your changes and offer feedback. Keep up the excellent work! Kindly remember to check our contributing guidelines |
Its feature Selection not election |
Can you contact me on discord or linkedin as well |
Yeah, I'll reach out to you on discord and LinkedIn, sorry for the typo 😅
…On Mon, May 20, 2024, 7:14 PM SrijanShovit ***@***.***> wrote:
Hey @SrijanShovit <https://github.com/SrijanShovit> , I am moving ahead
with the feature election as you mentioned yesterday, can you assign this
issue to me ?
Its feature Selection not election
Can you contact me on discord or linkedin as well
—
Reply to this email directly, view it on GitHub
<#119 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A36BDR2JBRR7GP5VDPXF3I3ZDH45TAVCNFSM6AAAAABH7X7LFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGQ4TGOJZGU>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
I have made a pull request on this particular issue, from where can I get
your discord ID, I have contacted you on Linkedin .
I had a doubt regarding the point allocation, in my first pr i didn't mark
done for the following four criteria:
- I have performed a self-review of my code
- I have commented my code, particularly in hard-to-understand areas
- My changes generate no new warnings
- I am working on this issue under GSSOC
- was I assigned points for that particular PR that was merged?
On Mon, May 20, 2024 at 7:24 PM Anurag Sarkar ***@***.***>
wrote:
… Yeah, I'll reach out to you on discord and LinkedIn, sorry for the typo 😅
On Mon, May 20, 2024, 7:14 PM SrijanShovit ***@***.***>
wrote:
> Hey @SrijanShovit <https://github.com/SrijanShovit> , I am moving ahead
> with the feature election as you mentioned yesterday, can you assign this
> issue to me ?
>
> Its feature Selection not election
>
> Can you contact me on discord or linkedin as well
>
> —
> Reply to this email directly, view it on GitHub
> <#119 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A36BDR2JBRR7GP5VDPXF3I3ZDH45TAVCNFSM6AAAAABH7X7LFGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQGQ4TGOJZGU>
> .
> You are receiving this because you were assigned.Message ID:
> ***@***.***>
>
|
I closed the previous pull request as I had to edit my code and have made another |
This issue has been automatically closed because it has been inactive for more than 7 days. If you believe this is still relevant, feel free to reopen it or create a new one. Thank you! |
Can you please assign this to me. |
This issue has been automatically closed because it has been inactive for more than 7 days. If you believe this is still relevant, feel free to reopen it or create a new one. Thank you! |
Hey @SrijanShovit , I am moving ahead with the feature election as you mentioned yesterday, can you assign this issue to me ?
The text was updated successfully, but these errors were encountered: