3f1e43b9c7
Mostly due to limited support for tables in rst format, information on labels used for Zephyr issues and pull requests in Github is hard to navigate and is visually not pleasing. Rearange the content of the section so that bullets are mainly utilized rather than tables. Format label names as 'emphasis', rather that 'monospace' (which should be used primarily for code snippets, and Github labels are not code). Also, group the information according to applicability (taking into account if a label is applicable to: * issues only; * pull requests only; * both issues and pull requests. Label names and decriptions are otherwise left 'as is' in this commit. Signed-off-by: Aleksandar Markovic <aleksandar.markovic.sa@gmail.com> |
||
---|---|---|
.. | ||
img | ||
code_flow.rst | ||
communication.rst | ||
dev_env_and_tools.rst | ||
documentation.rst | ||
index.rst | ||
issues.rst | ||
lts.svg | ||
milestones.jpg | ||
milestones2.jpg | ||
modifying_contributions.rst | ||
project_roles.rst | ||
proposals.rst | ||
pull_request_classes.png | ||
release_cycle.svg | ||
release_flow.png | ||
release_process.rst |