Add Issue and PR Templates similar to Resonate Frontend Repo

[M4dhav]

PR and Issue templates should be added to the Backend Repo similar to the frontend repo

[aditi25srivastava]

@M4dhav Heyy!!!!! I would love to work on this issue. Could you please assign it to me ?

[Chrahuldeveloper]

Please check : #97

[aditi25srivastava]

@M4dhav Heyyy!!!!! I have read through Pull Request #97 regarding adding issue and PR templates to the Resonate Backend repository. Before I start working on this I wanted to confirm if I should fork the Resonate-Backend repository to my own GitHub account and then create a branch to make the necessary changes?

let me know if this is the correct workflow or if there are any specific instructions you would like me to follow!!

[Chrahuldeveloper]

@M4dhav Hey i have resolved few issues u can check

[Chrahuldeveloper]

@M4dhav hey any update ??

[M4dhav]

Hey @aditi25srivastava , yes, you need to fork to your own GitHub and open PRs from there to contribute. It is your choice whether to make a new branch or not, however soon a dev branch will be added to this repo and future PRs will be required to contribute to that before main. However for now you can open it to main

[aditi25srivastava]

Heyy!!!! @M4dhav I've made the necessary changes. Do review it and lmk if I have to make any further changes!!

[aditi25srivastava]

Hey!!! @M4dhav I’ll need about a week to complete this, I’ll update you with my PR once it’s ready!! and I wanted to confirm if my recent approach is correct.... As per your last comment and the screenshot above, I see my PR is still including some commits from the previous contributor. I plan to create a fresh branch, cherry-pick only my own commits, and open a clean pull request as you suggested... Is this the correct step, or is there anything else I should take care of to ensure only my contributions are present in the PR?

[M4dhav]

Yeah this is the way I think would be best