docs: adding doc to inform of github dapr bot commands available in the repo (#527)

* adding doc to inform of github dapr bot commands available on the repo

* update statement based on doc

* addressing sign off issue
Signed-off-by: Author Name <[email protected]>

* trying to address the sign off

Signed-off-by: Esther Nwogu <[email protected]>

* ran pretty fix on the changes

Signed-off-by: Esther Nwogu <[email protected]>

* adding period at the end of statement

Signed-off-by: Esther Nwogu <[email protected]>

* adding doc to inform of github dapr bot commands available on the repo

Signed-off-by: Esther Nwogu <[email protected]>

* update statement based on doc

Signed-off-by: Esther Nwogu <[email protected]>

* addressing sign off issue
Signed-off-by: Author Name <[email protected]>

Signed-off-by: Esther Nwogu <[email protected]>

* trying to address the sign off

Signed-off-by: Esther Nwogu <[email protected]>

* ran pretty fix on the changes

Signed-off-by: Esther Nwogu <[email protected]>

* adding period at the end of statement

Signed-off-by: Esther Nwogu <[email protected]>

---------

Signed-off-by: Esther Nwogu <[email protected]>
Co-authored-by: Esther Nwogu <[email protected]>

Author: owate

daprdocs/content/en/js-sdk-contributing/js-contributing.md

@@ -103,6 +103,10 @@ Try to keep the first commit line short. This is harder to do using this commit
 concise and if you need more space, you can use the commit body. Try to make sure that the commit
 subject is clear and precise enough that users will know what change by just looking at the changelog.
 
+## Github Dapr Bot Commands
+
+Checkout the [daprbot documentation](https://docs.dapr.io/contributing/daprbot/) for Github commands you can run in this repo for common tasks. For example, you can run the `/assign` (as a comment on an issue) to assign issues to a user or group of users.
+
 ## Coding Rules
 
 To ensure consistency throughout the source code, keep these rules in mind as you are working: