Jim Huang
|
1d3943a72b
|
CI: Enforce newline at end of files
Reference:
https://medium.com/@alexey.inkin/how-to-force-newline-at-end-of-files-and-why-you-should-do-it-fdf76d1d090e
|
2024-06-21 16:39:05 +08:00 |
|
Jim Huang
|
c6b02adc98
|
CI: Only perform extensive checks on source file changes
|
2023-09-18 11:30:54 +08:00 |
|
Jim Huang
|
527e118da8
|
CI: Bump dependency versions
|
2023-09-18 02:05:28 +08:00 |
|
Jim Huang
|
1c916a79a9
|
CI: Bump validation host versioning
The CI is now running on Ubuntu 22.04-LTS along with gcc-11 and
clang-format-12 .
|
2022-12-10 06:21:02 +08:00 |
|
Jim Huang
|
c6b59d2a8f
|
CI: Bump dependency versions
|
2022-12-10 06:11:09 +08:00 |
|
Jim Huang
|
63ac35dd4f
|
CI: Bump dependency versions
|
2022-04-28 19:19:29 +08:00 |
|
linD026
|
d6e1044aa7
|
CI: introduce GCC static analysis
Since GCC version 10, there has been a new option -fanalyzer for
static analysis. It can make the CI pipeline more comprehensive.
Also, the static analysis updates in GCC 11, but we cannot install
the GCC 11 in ubuntu 20.04 straightforwardly right now, which is
the GitHub workflow environment (see status-check.yaml).
For this reason, we stay at the GCC 10.
Close #117
Reference
- https://gcc.gnu.org/onlinedocs/gcc-10.1.0/gcc/Static-Analyzer-Options.html
- https://developers.redhat.com/blog/2020/03/26/static-analysis-in-gcc-10
- https://lwn.net/Articles/870290/
- https://developers.redhat.com/blog/2021/01/28/static-analysis-updates-in-gcc-11
- 7d73c3e9c5
|
2021-10-08 19:41:22 +08:00 |
|
linD026
|
0d5ac2a5e2
|
CI: Enforce status checks once pull requests received (#113)
We tend to reject the pull requests if they fail to pass coding style checks
and static analysis.
See https://www.wesleyhaakman.org/working-with-pull-requests-status-checks-arm-templates-and-github-actions/
|
2021-09-23 20:01:13 +08:00 |
|