Add context param to check-team-membership.js and update calls

[praytoo]

Fixes #8201

What changes did you make?

• Added context parameter to check-team-membership.js
• Replaced hardcoded org with context.repo.owner
• Removed obsolete comment
• Updated verify-pr.js and issue-trigger.yml
• The issue mentioned updating post-to-skills-issue.js, but that file no longer exists in the repo. I searched the repo and updated all existing calls to checkTeamMembership and isMemberOfTeam to use the new context parameter.

Why did you make the changes (we will use this info to test)?

• I made these changes to refactor the check-team-membership.js utility so that it no longer uses a hardcoded org (hackforla). Instead, it now uses context.repo.owner, which makes the code more flexible and accurate across different repos.
• I also updated all calls to isMemberOfTeam and checkTeamMembership to include the new context parameter, ensuring consistency and avoiding errors.
• The issue also mentioned post-to-skills-issue.js, but that file no longer exists in the repo. I verified by searching the codebase, and I updated all other existing calls instead.

CodeQL Alerts

After the PR has been submitted and the resulting GitHub actions/checks have been completed, developers should check the PR for CodeQL alert annotations.

Check the PR's comments. If present on your PR, the CodeQL alert looks similar as shown

Please let us know that you have checked for CodeQL alerts. Please do not dismiss alerts.

• I have checked this PR for CodeQL alerts and none were found.
• I found CodeQL alert(s), and (select one):
  • I have resolved the CodeQL alert(s) as noted
  • I believe the CodeQL alert(s) is a false positive (Merge Team will evaluate)
  • I have followed the Instructions below, but I am still stuck (Merge Team will evaluate)

Instructions for resolving CodeQL alerts

If CodeQL alert/annotations appear, refer to How to Resolve CodeQL alerts.

In general, CodeQL alerts should be resolved prior to PR reviews and merging

Screenshots of Proposed Changes To The Website (if any, please do not include screenshots of code changes)

No visual changes to the website

[github-actions]

Want to review this pull request? Take a look at this documentation for a step by step guide!

---

From your project repository, check out a new branch and test the changes.

git checkout -b praytoo-add-context-to-check-team-membership gh-pages
git pull https://github.com/praytoo/website.git add-context-to-check-team-membership

[DDVVPP]

Review ETA: 6PM 08/22/25
Availability: 9AM-6PM M-F

[DDVVPP]

• The PR is done with the correct branch
• There is a linked issue
• The PR title accurately describes the issue
• Clear and through PR description

Thanks @praytoo ! A couple of comments:

• For some reason I don't see any of your changes in your branch or in this PR... have you pushed up all of your changes?
• It would be really nice to see the action items in the issue checked off so that it's clear that these items have been completed!

Thank you!

[praytoo]

@DDVVPP hello thank you for your feedback i've gone ahead and checked off the action items on the list like you suggested...and can you see if the changes are showing up on your end now? i believe i updated the pr to reflect the changes. thanks again!

[caz002]

Review ETA: 08/22/25
Availability: After 7PM on Weekdays

[caz002]

Thank you for your hard work on this issue @praytoo ! I have some changes to request, but afterwards I can approve your issue.

Things Done Well

• PR description accurately describes changes and why they were made
• Code does not trigger any QL alerts

Changes to Make

• I agree with DDVVPP in that I can't seem to see all the changes that you made. Only check-team-member.js is showing up in the "Files changed" tab on the pull request. Do you mind double checking again if you pushed all of your changes for verify-pr.js and issue-trigger.yml?
• In check-team-membership.js, I noticed you removed some of the lines and parameters in the commented block in the beginning. I think the instructions in the issue are to only modify/add the requested lines and leave the rest as-is.
• In check-team-membership.js, I think part of line 5 may have been accidentally deleted, and should be "Need read:org permission to use this function. Lack of permission will result in a 403 error."

[DDVVPP]

Hi @praytoo!
Following up on my previous comment, and agreeing with caz002, that some items seem to have perhaps been accidentally deleted in check-team-member.js, and the requested changes in the issue from the 4th checkbox onwards seem to be missing. Happy to approve once these updates have been made! Thank you!

[t-will-gillis]

Hey @praytoo This looks great! The branches are correct, you are linked to the original issue, you are describing what was done and why, you checked for CodeQL alerts, and you note that there are no visual changes. The context object is added to the files currently using check-team-membership.js and you made the edits requested by the issue.

One change is needed, and this isn't something you missed- it is because I misled you when I wrote the original issue.

• In the file check-team-membership.js, please replace the line for "org" and use instead:

  org: context.repo.owner,
  

I realized that context.repo.org would cause an error because the context.repo object only has an owner property, so org would cause an error. The replacement should work. My bad.

Except for the change, I tested this in my repo and the workflows appear to be working correctly. Thanks for working on this!

[praytoo]

hello @caz002 @DDVVPP @t-will-gillis thank you all for your valuable feedback i've gone ahead and applied all of those corrections and requested a re-review.

[caz002]

Thank you for making all of the changes @praytoo ! The pull request correctly modifies the files requested, and the description clearly describes the changes made. I approve this pull request.

[DDVVPP]

Thanks for all the changes @praytoo !
I'm approving these changes, but I do have one more question about a change in the check-team-membership.js file. The items in lines 7, 10, and 12 are missing the dashes, and I'm just curious about why those were elimated!
Thanks again!

[t-will-gillis]

Hi @praytoo Thank you for making the change- everything looks great!

I am Approving also, and I will merge this.

@DDVVPP I saw your note about the comments and removing the '-'. I can go either way about the dashes, however, I am also thinking that the comments after * @param {String} team ... are extraneous, and using JSDoc there should only be a simple, concise description of the function as the first line (before * @param {octokit} ...
@praytoo @DDVVPP @caz002, any thoughts about this? If needed, we can catch this in a new issue.

[praytoo]

I deleted the extraneous lines before but was corrected by @caz002 to keep those in about the "-" I didn't think it mattered because the "*" were there to bullet point the lines anyway @DDVVPP lmk what you think @t-will-gillis thanks everyone