Skip to main content

New Repository

Video walkthrough available here in Google Drive > Software > Azure Dev Ops > Resources

  • Login to [https://dev.azure.com/WorkflowDoctor/](https://dev.azure.com/WorkflowDoctor/)
  • Click the Create project button
  • Give the project a memorable name. If this is a code base for a specific client then the project should be named after the client. If the code base is for an internal tool it should be prefixed WFD. For cleanliness, any internal code bases have been grouped, if possible create the new repo within an existing projectWFD.Tools
  • WFD.AbbyyTools
  • Leave the visibility as private and the advanced section as is
  • Click create
  • On creation you will be moved into the repo itself, navigate to the Repositories > Files section on the left hand navigation panel
  • Clone the repository locally using your tool of choice
  • Once the repository has been cloned, add the standard git files from "G:\Shared Drives\Software\Azure Dev Ops\Standard_Repo". This should be a .gitignore, a NuGet.config, a scripts and src folder
  • Commit and push all files `(NOTE: It is very important to commit the gitignore file before adding any actual code)
  • Go to the Pipelines section in the Dev Ops Portal and click create a new pipelineWhere is your code - Azure Repos Git
  • Select your repository
  • Existing Azure Pipelines YAML file
  • Under branch master select /scripts/build/azure-pipelines.yml
  • Click save and run
  • Save changes
  • Start coding :) For details on the WFD branching and merging policy see here [https://drflow.freshdesk.com/a/solutions/articles/44000465928-branching-strategy](https://drflow.freshdesk.com/a/solutions/articles/44000465928-branching-strategy) 

For next steps once a repository has been created, please see [https://drflow.freshdesk.com/a/solutions/articles/44001777390-repository-best-practices](https://drflow.freshdesk.com/a/solutions/articles/44001777390-repository-best-practices) 

**` **