[riot-notifications] [RIOT-OS/RIOT] static-tests: group tests (#15803)
notifications at github.com
Tue Jan 19 18:04:12 CET 2021
The RIOT community cares a lot about code quality.
Therefore, before describing what your contribution is about, we would like
you to make sure that your modifications are compliant with the RIOT
coding conventions, see https://github.com/RIOT-OS/RIOT/wiki/Coding-conventions.
### Contribution description
Using the [`::group` command](https://docs.github.com/en/actions/reference/workflow-commands-for-github-actions#setting-an-output-parameter), the output of the static tests can be made a bit easier to scroll through and find issues, especially for runs that run on a base branch and not on a PR.
Put here the description of your contribution:
- describe which part(s) of RIOT is (are) involved
- if it's a bug fix, describe the bug that it solves and how it is solved
- you can also give more information to reviewers about how to test your changes
### Testing procedure
See https://github.com/miri64/RIOT/runs/1729102188 for an example run.
Details steps to test your contribution:
- which test/example to compile for which board and is there a 'test' command
- how to know that it was not working/available in master
- the expected success test output
### Issues/PRs references
Examples: Fixes #1234. See also #5678. Depends on PR #9876.
Please use keywords (e.g., fixes, resolve) with the links to the issues you
resolved, this way they will be automatically closed when your pull request
is merged. See https://help.github.com/articles/closing-issues-using-keywords/.
You can view, comment on, or merge this pull request online at:
-- Commit Summary --
* static-tests: group tests
-- File Changes --
M dist/tools/ci/static_tests.sh (11)
-- Patch Links --
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the notifications