repo setup

[sub1120]

@shivamvijaywargi we can put our suggestions and resources here about monorepo setup.

[shivamvijaywargi]

https://medium.com/@guysenpai89/nx-monorepo-publish-libraries-to-github-packages-with-github-actions-semantic-release-970883f2786a#:~:text=Your%20monorepo%20is%20commitizen%2Dfriendly,It%20also%20supports%20commitlint%20config.

[shivamvijaywargi]

https://blog.devgenius.io/automatic-semantic-versioning-and-commit-messages-semantic-release-and-commitizen-72e4eca5f194

[sub1120]

@shivamvijaywargi, I think you are right, monorepo does not have much use for us, and kind of overhead.

Can we move to other approach separate repo for frontend and backend?

If we both are good with separate repo approach,

Lets convert the current repo for frontend (because we already have issues created).
And we will make another repo for backend.

[shivamvijaywargi]

https://github.com/googleapis/release-please#setting-up-release-please

Please look at this and see if it is beneficial for us. If yes, can we use it?

[sub1120]

Ya, its good for release and version management, we can use it.

[shivamvijaywargi]

Please setup if possible, also rewrite the GH Action now that we have moved away from NX.

Thank you.

[sub1120]

sure I will check it.

[shivamvijaywargi]

The client setup has been completed from my end, please check if we are missing something or not.

[sub1120]

• Updated Branch protection rule (now owners also will not be able to push to the main branch accidentally)
• Added feature and bug issue template