hackforla / hackforla/VRMS

Create a Github Issue when a Non-Admin User Wants to Change a Restricted Project Field

Open
#796 7 comments 0 reactions 0 assignees View on GitHub
complexity: large Documentation feature: Github Actions role: Front End size: 2pt
Dominant language
JavaScript
Stars
61
Forks
101
PR merge metrics
No merged PRs in 30d

Description

### Overview
This builds on the work on PR #795

### Action Items

- [x] #1129
- [ ] When user clicks to make changes to the field a modal will open up to create an issue on the VRMS board.
- [ ] When the user clicks a field that they cannot edit, a modal pops up with a single input with a description of the proposed change.
- [ ] Creates an issue within VRMS and tag bonnie and other project leads, (then someone will sign off on it, and someone will go and make the change)
- Someone from the corresponding team will make the change.
- Post a comment on the related team's agenda indicating who requested the change and what change needs to be made. Bonnie will compile a list of issues for each agenda
- There is a closed pr with these changes started... https://github.com/hackforla/VRMS/pull/868
- [x] Rename team-lead-contact-info.md to project-edit-info.md
~~- [ ] Get text for .md file from Bonnie~~
~~- [ ] Update project-edit-info.md with new text~~
- [x] Change the link text to: "Click here to find out how to change this field"
~- [x] Make sure the link opens in a new tab~
- [x] Delete the md file that was created previously

Once the previous items have been merged
~~- [ ] - [ ] Change the link on editableField.js to point to the new .md file~~

### Resources/Instructions
To be able to post to the Github API you need to

- send a Personal Access Token (PAT) in the Authorization header of the API call function in the editableFiels.js named `requestToEdit`

- To obtain a PAT go in your Github account > Settings > Developer Settings > Personal Access Tokens > Generate New Token > enter a name for your token > Select Expiration > Select Scope (Repo) > Create Token

- Copy your token to a variable in you .env file because you will not be shown the token again

- Send in the API call Authorization header: `token ${PAT}`

Github Docs:
https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/creating-a-personal-access-token

client/src/components/manageProjects/editableField.js
~~team-lead-contact-info.md~~
PR #795

- https://docs.github.com/en/enterprise-server@3.0/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-url-query
- https://docs.github.com/en/rest/reference/issues#create-an-issue
- https://api.github.com/

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.