2529 GitHub get reactions from comment

[varshakumarr]

Fixes

This PR resolves #issue_number

What does this PR do?

(Provide a description of what this PR does and why it's needed.)

Screenshots

Provide supporting docs, limitations if any, video of the template, or anything that you want to share to support your PR

[gitguardian]

⚠️ GitGuardian has uncovered 12 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11548968	Triggered	GitHub Access Token	ff8ecad	GitHub/GitHub_Get_comments_for_issue.ipynb	View secret
11548968	Triggered	GitHub Access Token	ff8ecad	GitHub/GitHub_Get_comments_from_issue_in_a_given_repository.ipynb	View secret
11548968	Triggered	GitHub Access Token	ff8ecad	GitHub/GitHub_Get_reactions_from_comment.ipynb	View secret
11548968	Triggered	GitHub Access Token	c0e933a	GitHub/GitHub_Get_comments_and_reactions_from_issue.ipynb	View secret
11548968	Triggered	GitHub Access Token	c0e933a	GitHub/GitHub_Get_comments_from_issue.ipynb	View secret
11548968	Triggered	GitHub Access Token	c0e933a	GitHub/GitHub_Get_reactions_from_comment.ipynb	View secret
11748410	Triggered	GitHub Access Token	1e2f10c	GitHub/GitHub_Get_comments_and_reactions_from_issue.ipynb	View secret
11748410	Triggered	GitHub Access Token	93e13be	GitHub/GitHub_Get_comments_and_reactions_from_issue.ipynb	View secret
11748411	Triggered	GitHub Access Token	70ba52d	Naas/Naas_Add_or_Update_Secret.ipynb	View secret
11748411	Triggered	GitHub Access Token	70ba52d	Naas/Naas_Add_or_Update_Secret.ipynb	View secret
11748411	Triggered	GitHub Access Token	8dab024	Naas/Naas_Add_or_Update_Secret.ipynb	View secret
11748411	Triggered	GitHub Access Token	8dab024	Naas/Naas_Add_or_Update_Secret.ipynb	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}