Add new section "Testing Wins in a test repository" to the Wins Apps Script Development Wiki Page

[roslynwythe]

Overview

As developers we need to explore the feasibility of creating a WINS development environment which connects to a test repository, so that issues and pull requests generated during testing will be created in the contributors fork of the website repository rather than hackforla/website. The proposed strategy is to modify gh-requests and to replace the secret key with the contributor's PAT.

Action Items

• We are currently in the process of moving the old wiki to the new website-wiki repo, so we will not be making any changes or additions to the old wiki at this time. Thus, we will be adding wiki content through a different process now. Read How to Contribute to the Wiki
• In a comment in this issue, create a draft section "Testing WINS in a test repository" to be added to the Wins Apps Script Developement Guide¹. In it, detail instructions for using the developer's repository for testing Wins Apps Script code. The instructions should include these elements:
  • Generating a PAT (Personal Access Token) to replace the production repo secret key
  • creating branches for pushing updates to _wins-data.json and for testing JSON data
  • modifying code to push updates to the test branch
  • modifying code to create PR in the test repo instead of hackforla/website
  • modifying code to create issues in the test repo in response to new wins form submissions
• When the test environment is ready and the above elements can be demonstrated, move this issue to the "Questions/In Review" column and apply the "ready for dev lead" label.
• Demonstrate the above elements test for the dev lead.
• Upon approval from dev lead, add the link to the draft to How to Contribute to the Wiki

Dev Lead/Merge Team

• Be sure to revoke all access rights from the developer once copies of required documents have been made.

Resources/Instructions

Footnotes

1. Wins Apps Script Development Guide ↩

[github-actions]

Hi @roslynwythe.

Please don't forget to add the proper labels to this issue. Currently, the labels for the following are missing:
Complexity, Role, Feature

NOTE: Please ignore the adding proper labels comment if you do not have 'write' access to this directory.

To add a label, take a look at Github's documentation here.

Also, don't forget to remove the "missing labels" afterwards.
To remove a label, the process is similar to adding a label, but you select a currently added label to remove it.

After the proper labels are added, the merge team will review the issue and add a "Ready for Prioritization" label once it is ready for prioritization.

Additional Resources:

• Wiki: How to create issues
• Wiki: How to read and interpret labels