Slack Message Formatting

When composing Slack messages, use proper formatting:

Code & Technical Terms

• •Use backticks for: code snippets, function names, variable names, file paths, CLI commands, class names, package names
• •Example: "The fetchData function in src/api/client.ts returns a Promise"

Formatting Syntax

• •*bold* for emphasis or important terms
• •_italic_ for subtle emphasis
• •`code` for inline code
• •~strikethrough~ for corrections
• •> for quotes

Links

Link nouns, not verbs. Avoid calls to action.

• •

  Bad: "Pipeline 927888 is running. View Pipeline"

• •

  Good: "Pipeline 927888 is running."

• •

  Bad: "I opened a PR. Click here to review"

• •

  Good: "PR #123 is ready for review."

Azure DevOps Resources

Always link to Azure DevOps resources when mentioning them:

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

Best Practices

• •Keep messages concise and scannable
• •Use bullet points for lists
• •Mention users with @name only when their attention is needed