Workflow Modeling: GitHub
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 1
- Forks
- 1
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
### Overview
We need to model the GitHub management workflows, so that we can automate and/or train new people to do them.
### Action Items
- [ ] Name all of the known workflows in this tool
- [x] Make appointment with member of admin team who is currently performing function
- [x] Record workflow demos
- [x] Send admin assignee the link to the recording
- [x] Upload recording to Google Drive
- [x] Notify Bonnie to remove file to free up her Zoom account space
- [x] Attach link to issue
- [ ] Turn video transcript into step-by-step process confirmation
- [ ] Perform feasibility analysis to determine if automation possible, considering technology, time, and cost
- [ ] Depending on feasibility:
- [ ] Make automation
- [ ] Make a guide
### Resources/Instructions
- [Template for creating guides - WIP](https://docs.google.com/document/d/1-8gmeC-wnfM8C8fVvmTP1BLA2WfNjKH_XJrHB1OAV6Q/edit)
- [Recording of Bonnie and Glen's meeting on Sunday, June 27 ⋅ 5:30pm - 6:30pmm](https://drive.google.com/drive/folders/1C7UE9ZXfkdtKv62uVHZvbm8zVPW3sRJI)
Guía de contribución
Línea de trabajo
Start with the linked Google Drive recording and the guide template to identify and name the GitHub management workflows. Turn the transcript into step-by-step process documentation, then record the technology, time, and cost considerations for feasibility. Done means the workflows are documented and the issue's automation-versus-guide decision is addressed.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- github
- Área
- documentation
- Tipo de issue
- Documentación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 20/100