-
Notifications
You must be signed in to change notification settings - Fork 84
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
Create SECURITY.md #213
Create SECURITY.md #213
Conversation
Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for 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.
@Dipanita45 Please link the issue using keywords. (fixes/closes..) You can find the detailed info about the same here:
https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword
If needed, please check out merged PRs for reference.
Thanks & regards
I have uses fixes keyword |
@Dipanita45 Even if you have used it you haven't used it in right manner. Please refer to docs once on how to use it. If still have doubt please let me know! Thanks |
Please tell me how to use sir |
@Dipanita45 It looks like #212 also fixes the same issue. Please close one of the PRs |
I have closed
…On Fri, 8 Nov 2024, 8:08 pm Mayuresh Dharwadkar, ***@***.***> wrote:
@Dipanita45 <https://github.com/Dipanita45> It looks like #212
<#212> also fixes
the same issue. Please close one of the PRs
—
Reply to this email directly, view it on GitHub
<#213 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7SRZ6AO7RNSAXJY4JEPIXDZ7TEHNAVCNFSM6AAAAABRIZEUWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRUHEZDEOJTHE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Please merge #213 and label me level 2
On Fri, 8 Nov 2024, 8:09 pm Dipanita Mondal, ***@***.***>
wrote:
… I have closed
On Fri, 8 Nov 2024, 8:08 pm Mayuresh Dharwadkar, ***@***.***>
wrote:
> @Dipanita45 <https://github.com/Dipanita45> It looks like #212
> <#212> also
> fixes the same issue. Please close one of the PRs
>
> —
> Reply to this email directly, view it on GitHub
> <#213 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A7SRZ6AO7RNSAXJY4JEPIXDZ7TEHNAVCNFSM6AAAAABRIZEUWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRUHEZDEOJTHE>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Please merge my pull request and label me level 2 |
Please merge my pull request and label me level 2 |
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.
@Dipanita45 please sync your fork with the lates updates:
i had sync the fork @rohitinu6 @Mayureshd-18 |
@Dipanita45 please do it again |
Ok, I will do it.
…On Sat, 9 Nov 2024, 12:02 pm Rohit-Dubey, ***@***.***> wrote:
@Dipanita45 <https://github.com/Dipanita45> please do it again
—
Reply to this email directly, view it on GitHub
<#213 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7SRZ6E5QRT252TE6T6KM3DZ7WUABAVCNFSM6AAAAABRIZEUWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWGA3TONJUGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
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.
Looks good to me!
@Dipanita45 Why are there 2 PRs #212 and #218 ? They both fix the same issues... |
Please merge #213 and label me level 2
…On Sat, 9 Nov 2024, 7:23 pm Mayuresh Dharwadkar, ***@***.***> wrote:
@Dipanita45 <https://github.com/Dipanita45> Why are there 2 PRs #212
<#212> and #218
<#218> ? They
both fix the same issues...
—
Reply to this email directly, view it on GitHub
<#213 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A7SRZ6GG6UTJNDS4OZQIMELZ7YHVPAVCNFSM6AAAAABRIZEUWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWGIZDKMJXGY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Please
On Sat, 9 Nov 2024, 7:29 pm Dipanita Mondal, ***@***.***>
wrote:
… Please merge #213 and label me level 2
On Sat, 9 Nov 2024, 7:23 pm Mayuresh Dharwadkar, ***@***.***>
wrote:
> @Dipanita45 <https://github.com/Dipanita45> Why are there 2 PRs #212
> <#212> and #218
> <#218> ? They
> both fix the same issues...
>
> —
> Reply to this email directly, view it on GitHub
> <#213 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/A7SRZ6GG6UTJNDS4OZQIMELZ7YHVPAVCNFSM6AAAAABRIZEUWGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRWGIZDKMJXGY>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
|
Please please merge my pull request and label me level 2 |
@Dipanita45 as I mentioned earlier, you need to sync your fork to get your PR mergerd and you have not done it yet: Please let me know if you are facing any issue with this |
Added the security for the website
Fixes: #212 #209
Please merge my pull request and label me level2
@rohitinu6