🚧: Stale Prs

[rubiin]

I think its time to merge/close Prs that have been stale for too long . Most of them have merge conflicts which are restricting them from being merged while some have some small changes to be made.
Lets use this issue to report, and if needed reassign and merge them. Anyone upto the challenge , feel free to drop in the issue before you get started :)

Please find the list below:
https://github.com/validatorjs/validator.js/pulls?q=is%3Apr+is%3Aopen+review%3Achanges-requested+sort%3Acreated-asc
https://github.com/validatorjs/validator.js/pulls?q=is%3Apr+is%3Aopen+label%3Amc-to-land+sort%3Acreated-asc

[rubiin]

A starting measure to find stale prs is to find prs with change requested status over 1+ years of no response from author

[profnandaa]

Also good ones are mc-to-land, meaning they were already reviewed and just waiting for the merge-conflict fix. But I see that they are now few, so it's better to focus on the change requested ones that you shared.

[rubiin]

Updated the description to include both

[Daniyal-Qureshi]

@profnandaa Can I start working on this?
#2328

[rubiin]

You can take it

[THILAK6]

@rubiin Can I pick this? #2033

[rubiin]

You can go for it

[bmonish]

@rubiin I'm sorry if I sound dumb, but how would we contribute to the same PR and resolve conflicts if they were raised from other people's fork? Are we supposed to create our own fork and copy the changes from the Original PR?

[rubiin]

Yeah . Create your own fork, commit the changes done by the original author and resolve the merge conflicts in your own fork.

[bmonish]

Yeah . Create your own fork, commit the changes done by the original author and resolve the merge conflicts in your own fork.

Understood. Thanks for clarifying

[Suven-p]

@rubiin Can I do #2019 ?

[rubiin]

@Suven-p go for it

[mrpmohiburrahman]

Hi, @rubiin ,
I have fix this PR #2062,
Here is my PR #2475

Please, have a look.