[castillios]

Fixes #8701

What changes did you make?

• gh-requests/Code.js:
  • Replace addIssueToProjectBoardColumn function with addIssueToProjectV2 to post issues to the current project board using a GraphQL API call
  • Create a graphqlRequest_ helper function to build an API call. It mirrors the existing postRequest_ function
  • Remove any console output of GitHub PAT to avoid leaking sensitive keys
• wins-form-responses/Code.js:
  • Update docs comment to point to github-actions/utils/_data/status-field-ids.js for accuracy
  • Replace outdated COLUMN_KEYS with PROJECT_V2 object literal, which connects to current project board
  • Update previously hardcoded display-column filter in order to maintain PR creation
  • In createIssue replace addIssueToProjectBoardColumn with call to addIssueToProjectV2

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

• To keep the Wins workflow up to date by notifying the team of any new Wins submissions via automated issue and PR creation
• Why shift to GraphQL?: GitHub previously used REST for any Project Board API calls. However, they rolled out a new Projects v2 feature that requires GraphQL. Hack for LA uses a Projects v2 board, and because the older flow relied on deprecated Projects classic code, the automated notification workflow stopped working.
• As for why the change to the hardcoded display-column filter was made, Danielle proposed the change and why in the original issue.

Testing Setup/Strategy

• Following the Wins Google Apps Script Development Guide, I created copies of the Wins responses Sheet & gh-requests Apps Scripts
• In order to test the Wins workflow, I replaced any points that touch Hack for LA's project boards and the elizabethhonest account with my fork's project board IDs and my own GitHub handle respectively
• This was the following testing flow I used (as per section 8. Testing of the guide):
  • On my fork, create an update-wins-data branch to receive Wins submissions / data from Google Apps Script.
  • Then create a test-wins branch to act as the base for PRs in place of gh-pages
  • Submit a Win via my copy of the Wins Google Form
  • Ensure for every Wins submission, an issue is created in my fork, for example: Review Needed - New Wins Form Submission castillios/website#35
  • Run main() on wins-form-response/Code.js via Google Apps Script to create a PR on my fork: (Update wins-data.json via Google Apps Script castillios/website#36).
• Then, I merged the test PR into test-wins and viewed the website to ensure that test Wins populate the page as intended (screenshot attached below)

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)

Note: These are NOT current changes to the website, rather the screenshots below are examples of what the changes WOULD look like after the refactor using test Wins.

Example of Wins Page

Wins test submissions via Google Sheets

I've highlighted the Wins overview to emphasize these are the same submissions displayed in the example above:

[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 castillios-refactor-wins-workflow-8701 gh-pages
git pull https://github.com/castillios/website.git refactor-wins-workflow-8701

[daras-cu]

@castillios everything looks good with your changes, I tested the Wins workflow in my dev environment and confirmed:

• New Wins form submissions populate the spreadsheet correctly
• A wins review issue is created upon form submission and moved to the proper column on the Project Board
• When running the main function, a PR is opened with the new entries, correctly formatted
• The encoded PAT is no longer output in the console
  Thank you for working on this and your patience while I figured out some of the problems!

[daras-cu]

@ExperimentsInHonesty as part of the changes in this PR, the elizabethhonest bot access token will need to have "project" permissions added to its scope. This will allow it to add Wins review issues to the correct column on the project board using the new GraphQL request. Please let me know if it is alright to change the permissions on the elizabethhonest token.

[Tomlu60220244]

Availability: Weekends
ETA: 10/11/2026

[Tomlu60220244]

Hi castillos! Sorry for the delay review. I checked your code and everything is great. You did an excenlent job!
I love that the old project-board function is no longer referenced and that you replaced the deprecated Projects Classic workflow with the new Projects v2 GraphQL flow.
There are just few trailing whitespaces , but they do not affect the functionality of this change.
I will approve this PR. Great work!

[castillios]

Thank you @daras-cu and @Tomlu60220244 for the feedback!

[ExperimentsInHonesty]

@daras-cu yes, please go ahead

@ExperimentsInHonesty as part of the changes in this PR, the elizabethhonest bot access token will need to have "project" permissions added to its scope. This will allow it to add Wins review issues to the correct column on the project board using the new GraphQL request. Please let me know if it is alright to change the permissions on the elizabethhonest token.

[daras-cu]

I've updated the elizabethhonest bot token with the "project" permission, and tested the workflow to confirm it is working.