CI Docs: Using an inclusive linter

[jeremydelacruz]

Pull Request Template

What are you trying to address

• Add content around using an inclusive linter in CI pipelines
• Addresses inclusive-dev-tools issue Make contribution to playbook around woke and using an inclusive linter  inclusive-dev-tools/woke#35

Description of new changes

• Adding new markdown file in docs/continuous-integration/inclusive-linting.md
• Adding content around what inclusive linting is, how it can be useful, and how to get started with an inclusive linting tool

For all pull requests

• Link to the issue you are solving (so it gets closed)
• Label the pull request with the appropriate area(s)
• Assign potential reviewers (you may also want to contact them on Teams to ensure timely reviews)
• Assign the project - Engineering Playbook Backlog
• Assign the pull request to yourself

[kevinleung23]

I love the addition of this into the playbook, thanks for writing this up. I appreciate that you list the benefits and point the developers to the source to learn more.

[madossan01]

Love to see this guidance for CI. Thanks to propose and create the document.

[fnocera]

Looks great @jeremydelacruz! I would also look for somewhere we can link to this document from within the main CI guidance page.

[mkcomer]

Looks great! Thanks for adding CI section. Suggested an additional link - action for woke w/ review dog

[jeremydelacruz]

@fnocera @madossan01 thanks for the reviews! The markdown-link-check step seems to keep failing on the following two links from ./docs/source-control/README.md (though they seem to be working links):

• https://www.pluralsight.com/courses/master-git
• https://www.pluralsight.com/courses/how-git-works

They're referenced in docs unrelated to my changes, but I wanted to flag it. Do we think I should hold off on merging?