Instructions for What to Do With "Update Project Profile" ERs
- Dominant language
- JavaScript
- Stars
- 363
- Forks
- 872
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 18
Description
### Overview
We need instructions for PMs and leads on what to do with "Update Project Profile" ERs or epics with sub-issue(s) that have already been written so that PMs and leads know how to manage these types of ERs or epics.
### Action Items
- [ ] Copy and paste the instructions from the template in the "Resources/Instructions" section below in a new comment.
- [ ] In the comment you just created, follow the instructions.
### Resources/Instructions
#### Template
```
### Action Items
- [ ] For each requested change in the ER or epic, check that an issue has been created for it.
- [ ] Make sure all the issues created from the Update Project Profile ERs are added to the ER or epic as a sub-issue.
- [ ] Once all the issues for the requested changes have been made, the ER or epic can be closed with a note to the author to check the sub-issues for completion.
- [ ] Once the ER or epic is closed, for each sub-issue author, add them back as assignees to the ER so they get credit for working on the ER.
```
- Project Board filtered to display "Update Project Profile" issues and ERs: https://github.com/orgs/hackforla/projects/86/views/1?filterQuery=%22Update+Project+Profile%22
Contributor guide
Assessment
This issue has not been assessed yet.