[Docs] [Developer Policy] Document best practice of not tagging a username in commit messages and PR descriptions (#164328)

Related to:
https://discourse.llvm.org/t/forbidding-username-in-commits/86997

**Context:**

When we merge a commit including tag to another username (e.g.
`@<someUser>`), that account will receive an email / notification every
time that PR is cherry-picked and pushed to a fork, generating _a lot_
of spam in the user's inbox. As of today, there's no way of disabling
this on GitHub settings.

**This PR** documents this error in our developer policy, and reminds
contributors to avoid it.

**Next steps:** I'm a big believer that any policy that is not enforced
via automation is not enforced at all, so I'd love to see some kind of
check to prevent this error. However, there does not seem to be an
agreement to do that _yet_. I'll see if I can gather support for doing
that.

---------

Co-authored-by: Jakub Kuderski <kubakuderski@gmail.com>
1 file changed
tree: 90a04907ef5461215d2c53be5bf9aa9812e8b91c
  1. .ci/
  2. .github/
  3. bolt/
  4. clang/
  5. clang-tools-extra/
  6. cmake/
  7. compiler-rt/
  8. cross-project-tests/
  9. flang/
  10. flang-rt/
  11. libc/
  12. libclc/
  13. libcxx/
  14. libcxxabi/
  15. libsycl/
  16. libunwind/
  17. lld/
  18. lldb/
  19. llvm/
  20. llvm-libgcc/
  21. mlir/
  22. offload/
  23. openmp/
  24. orc-rt/
  25. polly/
  26. runtimes/
  27. third-party/
  28. utils/
  29. .clang-format
  30. .clang-format-ignore
  31. .clang-tidy
  32. .git-blame-ignore-revs
  33. .gitattributes
  34. .gitignore
  35. .mailmap
  36. CODE_OF_CONDUCT.md
  37. CONTRIBUTING.md
  38. LICENSE.TXT
  39. pyproject.toml
  40. README.md
  41. SECURITY.md
README.md

The LLVM Compiler Infrastructure

OpenSSF Scorecard OpenSSF Best Practices libc++

Welcome to the LLVM project!

This repository contains the source code for LLVM, a toolkit for the construction of highly optimized compilers, optimizers, and run-time environments.

The LLVM project has multiple components. The core of the project is itself called “LLVM”. This contains all of the tools, libraries, and header files needed to process intermediate representations and convert them into object files. Tools include an assembler, disassembler, bitcode analyzer, and bitcode optimizer.

C-like languages use the Clang frontend. This component compiles C, C++, Objective-C, and Objective-C++ code into LLVM bitcode -- and from there into object files, using LLVM.

Other components include: the libc++ C++ standard library, the LLD linker, and more.

Getting the Source Code and Building LLVM

Consult the Getting Started with LLVM page for information on building and running LLVM.

For information on how to contribute to the LLVM project, please take a look at the Contributing to LLVM guide.

Getting in touch

Join the LLVM Discourse forums, Discord chat, LLVM Office Hours or Regular sync-ups.

The LLVM project has adopted a code of conduct for participants to all modes of communication within the project.