Azure DevOps Formatting

When interacting with Azure DevOps, use proper formatting:

Code & Technical Terms

• •Use backticks for: branch names, file paths, function names, variable names, CLI commands
• •Example: "Merge feature/auth into master after fixing AuthService.ts"

Always Link Resources

Link PRs, pipelines, and work items when mentioning them:

• •PRs: "PR #12345"
• •Pipelines: "Pipeline 927888"
• •Work items: "Bug #5678"

Links

Link nouns, not verbs. Avoid calls to action.

• •

  Bad: "The build failed. View Pipeline"

• •

  Good: "Pipeline 927888 failed."

• •

  Bad: "I created a work item. Click here"

• •

  Good: "Bug #5678 tracks this issue."