Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine

DRC Debugs - Investigate Automatically Creating New Question Doc using Google API

Open
#2,599 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

back-end difficult spike
Dominant language
TypeScript
Stars
36
Forks
9
Avg merge
4d 21h
Merged PRs (30d)
11

Description

Investigate how to make a new copy of the design review question doc, store it in the NER google drive, and link it to the Design Review when scheduling a design review instead of making the user copy the doc and enter the link themselves. This should definitely be possible, in fact our API key for google might already have the permissions to do it, but you'll definitely need to look into the google cloud setup, you'll need the NER gmail login (https://console.cloud.google.com/apis/credentials/consent?project=nerpm-318216). Ideally the new doc would even have the name of the created design review filled in where it should be and the name of the file should have the name of the design review as well.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by investigating the design-review scheduling flow and the Google Cloud API credentials/consent setup for project nerpm-318216. Determine whether the existing API key can copy the design review question document into the NER Google Drive and update the scheduled review with its link. Done means the document is created automatically, named for the design review, includes its name where appropriate, and the link is stored without manual copying.

Written by the indexing model from the issue text.

Assessment

Tech stack
google-cloud, typescript
Domain
api, cloud
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.