-
-
Notifications
You must be signed in to change notification settings - Fork 777
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add new fields to WINS Display Review and _wins-data.json #5472
Open
1 of 16 tasks
Labels
Complexity: Large
P-Feature: Wins Page
https://www.hackforla.org/wins/
Ready for Prioritization
role: back end/devOps
Tasks for back-end developers
size: 3pt
Can be done in 13-18 hours
Milestone
Comments
roslynwythe
added
Feature Missing
This label means that the issue needs to be linked to a precise feature label.
role missing
size: missing
labels
Sep 10, 2023
This comment has been minimized.
This comment has been minimized.
roslynwythe
added
Complexity: Large
P-Feature: Wins Page
https://www.hackforla.org/wins/
role: back end/devOps
Tasks for back-end developers
size: 2pt
Can be done in 7-12 hours
Draft
Issue is still in the process of being created
and removed
Feature Missing
This label means that the issue needs to be linked to a precise feature label.
role missing
size: missing
labels
Sep 10, 2023
This was referenced Sep 10, 2023
kimberlytanyh
added
the
Dependency
An issue is blocking the completion or starting of another issue
label
Sep 10, 2023
ExperimentsInHonesty
added
ready for dev lead
Issues that tech leads or merge team members need to follow up on
and removed
Dependency
An issue is blocking the completion or starting of another issue
labels
Jan 24, 2024
This comment was marked as duplicate.
This comment was marked as duplicate.
2 tasks
roslynwythe
added
Ready for Prioritization
and removed
Draft
Issue is still in the process of being created
ready for dev lead
Issues that tech leads or merge team members need to follow up on
labels
Jan 26, 2024
This comment has been minimized.
This comment has been minimized.
roslynwythe
added
Ready for Prioritization
and removed
ready for dev lead
Issues that tech leads or merge team members need to follow up on
labels
Oct 15, 2024
ExperimentsInHonesty
added
ready for dev lead
Issues that tech leads or merge team members need to follow up on
Draft
Issue is still in the process of being created
and removed
Ready for Prioritization
labels
Oct 15, 2024
This comment was marked as outdated.
This comment was marked as outdated.
roslynwythe
added
Ready for Prioritization
and removed
Draft
Issue is still in the process of being created
ready for dev lead
Issues that tech leads or merge team members need to follow up on
labels
Nov 3, 2024
ExperimentsInHonesty
added
Draft
Issue is still in the process of being created
and removed
Ready for Prioritization
labels
Nov 5, 2024
This comment was marked as outdated.
This comment was marked as outdated.
roslynwythe
added
Ready for Prioritization
and removed
Draft
Issue is still in the process of being created
labels
Nov 8, 2024
This comment was marked as outdated.
This comment was marked as outdated.
ExperimentsInHonesty
added
ready for dev lead
Issues that tech leads or merge team members need to follow up on
Draft
Issue is still in the process of being created
Added to dev/pm agenda
and removed
Ready for Prioritization
labels
Nov 12, 2024
19 tasks
roslynwythe
removed
ready for dev lead
Issues that tech leads or merge team members need to follow up on
Added to dev/pm agenda
Draft
Issue is still in the process of being created
labels
Nov 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Complexity: Large
P-Feature: Wins Page
https://www.hackforla.org/wins/
Ready for Prioritization
role: back end/devOps
Tasks for back-end developers
size: 3pt
Can be done in 13-18 hours
Dependency
Overview
We need to create new fields to hold only GitHub and LinkedIn handles (in contrast to the current fields which contain complete URLs), and to incorporate those fields into the Response sheet, Review sheet, and the _wins-data.json feed.
Details
We set up validation on the wins form so that users could give us the handles, with and without URL prefixes, now we need to take only the handle into the relevant sheets, so that we can (in another issue) update the .js files.
Ultimately, the goal is to have the URLs on the wins page (you can see them when you hover over the LinkedIn and GitHub icons), have a standard format. See epic for more details.
Action Items
wins-form-responses
within the Wins-form (responses)1 sheet, but you will require a Google Drive test environment that includes copies of Wins-form (Responses)1, gh-requests2, and Wins-form[^6]. It will also be useful to read Wins Form Admin Guide3. It will also be necessary to setup a test environment in your GitHub repository. Follow instructions in the comment in the Hfla Google Apps Script Development Process Guide4 and Testing WINS in a test repository5Wins-form
, including the issue # in the name, then share that copy with the developer as EDITOR.Responses
settings of theWins-form
so that test submissions will be stored in the Wins-form (Responses} that is in the test environmentinsertLatestFormSubmitIntoReviewSheet
andcreateIssue
functions will execute when a form is submittedmain()
for testing, you must follow instructions in Testing WINS in a test repositoryclasp
utility can be used to transfer code back and forth between the local worksation and the Google Drive as needed.Response
sheet, create two new columnsGitHub-handle
andLinkedIn-name
insertLatestFormSubmitIntoReviewSheet
populate the new columns with strings extracted from the submitted data in theGitHub URL
andLinkedIn URL
columns in theResponse
sheet.GitHub-handle
andLinkedIn-name
, along with the submitted data forGitHub URL
andLinkedIn URL
, on the Review sheet.main
add code to include theGitHub-handle
andLinkedIn-name
fields in _wins-data.jsonCode.js
and creating a pull request.Resources/Instructions
Footnotes
Wins-form (Response) Sheet ↩ ↩2 ↩3
gh-requests ↩
Wins Form Admin Guide ↩ ↩2
Hfla Google Apps Script Development Process Guide - draft ↩ ↩2 ↩3 ↩4
Testing WINS in a test repository ↩
The text was updated successfully, but these errors were encountered: