Fix/Workflows: Auto Response Workflow

[haideralipunjabi]

Please describe the changes this PR makes and why it should be merged:

Status

• Code changes have been tested against prettier, or there are no code changes
• I know how to update typings and have done so, or typings don't need updating

Semantic versioning classification:

• This PR changes the codebase
  • This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
  • This PR changes the internal workings with no modifications to the external API (bug fixes, performance improvements)
• This PR only includes non-code changes, like changes to documentation, README, etc.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
million-kitchen-sink	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 8, 2023 4:17pm
sink	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 8, 2023 4:17pm

[CLAassistant]

All committers have signed the CLA.

[coveralls]

Pull Request Test Coverage Report for Build 6801000106

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall first build on main at 25.706%

---

Totals
Change from base Build 6800519726:	25.7%
Covered Lines:	1257
Relevant Lines:	5082

---

💛 - Coveralls

[tobySolutions]

Hey there @haideralipunjabi, you changed it from pull_number to issue.number? May I ask why?

[haideralipunjabi]

Hey there @haideralipunjabi, you changed it from pull_number to issue.number? May I ask why?

Sure. The action uses actions/github-script and from its documentation I found out that that context variable doesn't have any property called pull_request, it only has issue as a property.

On studying the actual code of the context variable, you can see that issue.number actually returns both pull request number of issue number based on what is available

[tobySolutions]

Hey there @haideralipunjabi, you changed it from pull_number to issue.number? May I ask why?

Sure. The action uses actions/github-script and from its documentation I found out that that context variable doesn't have any property called pull_request, it only has issue as a property.

On studying the actual code of the context variable, you can see that issue.number actually returns both pull request number of issue number based on what is available

Hmm, thank you very much Haider and the auto labelling issue?

[haideralipunjabi]

Hey there @haideralipunjabi, you changed it from pull_number to issue.number? May I ask why?

Sure. The action uses actions/github-script and from its documentation I found out that that context variable doesn't have any property called pull_request, it only has issue as a property.
On studying the actual code of the context variable, you can see that issue.number actually returns both pull request number of issue number based on what is available

Hmm, thank you very much Haider and the auto labelling issue?

Separate PR #824

[tobySolutions]

Hey there @haideralipunjabi, you changed it from pull_number to issue.number? May I ask why?

Sure. The action uses actions/github-script and from its documentation I found out that that context variable doesn't have any property called pull_request, it only has issue as a property.
On studying the actual code of the context variable, you can see that issue.number actually returns both pull request number of issue number based on what is available

Hmm, thank you very much Haider and the auto labelling issue?

Separate PR #824

Oh, ok. I'm gonna merge this to see what happens.