Migrating Engineering Guides to New Repo

[JesseTheCleric]

Overview

We need to move all existing guides to the new repository for guides and templates (knowledgebase-content)

Prerequisite

You need to have

• Manager access to the following drives
  • CoP Google Drives
  • KB-content drive
• Admin access for the repos the issues are in

Action Items

Use the Guide below to migrate all guides related to UI/UX from CoPs to knowledgebase-content. (e.g., there might be a research guide that is relevant to product in the UI/UX community of practice).

• Do steps 1-5
• Add a comment below with the heading and add a link to each of the issues you moved for that CoP

### Guides that are ready to move for lead review
- #

• Move this issue to the Questions/Review column on project board and add the label ready for pm lead
  • Message the lead in the Guides Slack channel by sending a link to the comment with the issues
• lead will sign-off if the issues are ready to move
• once you get sign-off, you can move the issue (step 6 in the guide)
• Check wikis/other resources for references to guides by numbers or names, so no links end up broken
• When you are done, go to Clean Up Guide Issues for Triage #174 and check off the dependency. If all other dependencies are checked off already, then move that issue into the new issue approval column and add it to the team agenda Guides: Meeting Agenda & Minutes #136

Resources/Instructions

• Epic for all CoP guides moves: CoP Templates and Guides Board Migration #169
• Repo: knowledgebase content repo
• Repo Engineering CoP Repo
  • Repo, Issue Tab: Search for guides that have not been moved to the Knowlegebase repo
    • Repo, Issue Tab, "Create a Guide" only issue Search for guides that have not been moved to the Knowlegebase repo
• Google Drive: Knowledgebase-content
• Project Board: Guides: Knowledgebase Content Tracker
• Form: Guides Migration Google Form
• Spreadsheet: New Guide Tracker (WIP)
• Guide: How to Move a Guide to a New Repo

[fchan218]

Issues that need to be checked prior to Steps 1-5 for migration into knowledgebase content repo

Check off the issues that can be migrated

• Create a Guide/Template: Using Docker engineering#93
• Create a Guide/Template: Systems Diagram engineering#37
• Create a Guide/Template: Interview Practice engineering#33
• Create a Guide/Template: Documentation Technologies engineering#29
• Create a Guide/Template: Compilation with Webpack engineering#28
• Create a Guide/Template: Testing GitHub actions in your own repository engineering#27
• Create a Guide/Template: Decision Records engineering#26
• Create a Guide/Template: CI/CD with GitHub actions engineering#25
• Create a Guide/Template: Implementing Tests with Your Code Changes engineering#19
• Create a Guide/Template: Setting up Git engineering#16
• Create a Guide/Template: Agile Development/Scrum/Kanban engineering#15
• Create a Guide/Template: Professional Development engineering#14
• Create a Guide/Template: Site Architecture Documentation engineering#3
• Create a Guide/Template: Making a good CONTRIBUTING doc for your project's github repo engineering#2

[ExperimentsInHonesty]

This epic has one new issue which I have moved, but it will need reformatting

• docs: How to resolve PR merge conflicts when another contributor made a previous PR knowledgebase-content#120