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
c6b02adc98
CI: Only perform extensive checks on source file changes
2023-09-18 11:30:54 +08:00
527e118da8
CI: Bump dependency versions
2023-09-18 02:05:28 +08:00
3c66525ef2
Delete old release and retag latest commit
...
This ensures the latest commit message and timestamp can be correctly
included in the release.
2023-07-04 00:36:05 +08:00
fe46d27faf
Revert "Delete existing release asset before releasing"
...
This reverts commit 7ee66c559ff12c254d04c65c54325acbb655133a.
2023-07-03 09:32:35 +08:00
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
c6b59d2a8f
CI: Bump dependency versions
2022-12-10 06:11:09 +08:00
0fe984fd04
Make the naming for GitHub Actions more consistent
2022-12-10 06:07:56 +08:00
63ac35dd4f
CI: Bump dependency versions
2022-04-28 19:19:29 +08:00
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
76c7b0edbd
Keep workflow running even if no release tag found
...
The action we used to delete the old release somehow cannot find the
release tag in forked repo and cause the workflow failed.
To solve this issue, simply setting `fail-if-no-release` option to false
will do the trick.
2021-09-24 13:34:32 +08:00
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
5070fcd9d0
CI: Run static analysis with Cppcheck ( #105 )
...
Cppcheck[1] is integrated into CI pipeline for running static analysis.
However, Cppcheck is known to report false-positive, and we have to
suppress some warnings in advance.
[1] https://cppcheck.sourceforge.io/
2021-09-14 00:52:04 +08:00
a1aa18efe0
Trivial GitHub workflow tweak
2021-09-13 06:41:47 +00:00
3fcbb8e182
Improve CI pipeline to automate module testing ( #95 )
...
The script executes insmod/rmmod twice with available kernel modules.
Close #72
2021-09-08 20:38:50 +08:00
2db805da2c
Check coding style in CI
2021-08-17 13:07:06 +08:00
f6ee284894
Temporary fix release action failed issue
2021-08-09 13:04:12 +08:00
8f32341bee
Fix alignment problem in code block ( #45 )
...
In rendered HTML, the line number should be right aligned, and
code should be left aligned accordingly.
In addition, this patch added the basic build instructions, so that
someone can generated the PDF and HTML files.
Close #44
2021-08-08 01:29:50 +08:00
937acfa0d7
Publish GitHub Page with GitHub Action
...
Add a new Github Action to publish to the GitHub page. Use twtug/lkmpg
image for reproducibility.
Ref:
- sysprog21#27
- https://github.com/TeXtw/docker-lkmpg
2021-08-02 06:22:29 +01:00
7ee66c559f
Delete existing release asset before releasing
...
Use mknejp/delete-release-assets to delete existing asset.
This approach might not be optimal if softprops/action-gh-release
supports upserting [1].
[1] https://github.com/softprops/action-gh-release/pull/134
2021-08-01 21:05:47 +08:00
0fce98f6d2
Dockerized PDF deployment in GitHub Actions ( #28 )
...
Add a new GitHub Action to build and release the PDF file after every
push to master. Use texlive/texlive docker image for the sake of
reproducibility in preparation for future build tools like make4ht .
Progress #27 - Reproducible TeX build environment using Docker
2021-08-01 19:39:12 +08:00
