--- tags: v3, dragons, processes --- # v3 GitHub ## Branches What is our branching strategy? ## Templates and Workflows Now that we've been using our processes we can look to add templates and workflow integrations and automations to streamline things. Many of the templates and GitHub Actions workflows we create are version controlled and live directly in our monorepos in the `.github` folder. This allows for us to tweak and adjust as we grow and also provides a way for us to share them with other folks in the space. **Relevant Issues**: - [Create and add issue and PR templates (Rage) #42](https://github.com/HausDAO/daohaus-rage/issues/42) - [Create and add issue and PR templates (Sage) #20](https://github.com/HausDAO/daohaus-monorepo/issues/20) - [Create Issue Templates for Components #34](https://github.com/HausDAO/daohaus-monorepo/issues/34) - [Add Issue template for Component Library #19](https://github.com/HausDAO/daohaus-monorepo/pull/19) - This PR is a starting point -- we can revisit it and change the template to include some additional information to support our general workflows - [Research and document Github Projects Workflows #33](https://github.com/HausDAO/daohaus-monorepo/issues/33) ### Issue Templates We can create as many issue templates as we want to use. We can split these across Rage and Sage, or focus on the *type* of issue such as *Component Library Issue* that would be the same for Rage and Sage. We can autocomplete fields as `title` and `label` such as adding `haus-components` and `sage` labels to any Sage Component Library issue. ### PR Templates We can add PR templates and add them to our `.github` folder on the Rage and Sage monorepos. These will then be automatically used as a template when folks create a PR. Once we have the PR templates in place we can add automations to our workflow such as indiciating that something is ready for Review. ### Workflows: Automations and Integrations Working Doc: [GitHub Projects Automations](https://hackmd.io/mncFghtsQsqwYwq1VO_KSg) - Will combine this into as we work -- mainly wanted a working doc for the research and ideas. Do we need to add a step for deleting branches or will this be automated? ## TODOs - [x] Review and add Component Library Issue Template - [x] Add initial Rage PR template for review - [x] Add initial Sage PR template for review - [x] Continue to explore GitHub Projects automations - [ ] Add notificaiton to Discord for when cards move to *Review*