summaryrefslogtreecommitdiff
path: root/.github
AgeCommit message (Collapse)Author
2023-10-29Add CodeQL Workflow for Code Security AnalysisBrian
Add CodeQL Workflow for Code Security Analysis This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats. We added a new CodeQL workflow file (.github/workflows/codeql.yml) that - Runs on every pull request (functionality to run on every push to main branches is included as a comment for convenience). - Runs daily. - Excludes queries with a high false positive rate or low-severity findings. - Does not display results for git submodules, focusing only on our own codebase. Testing: To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code. Deployment: Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps: 1. Under the repository name, click on the Security tab. 2. In the left sidebar, click Code scanning alerts. Additional Information: - You can further customize the workflow to adapt to your specific needs by modifying the workflow file. - For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation (https://codeql.github.com/ and https://codeql.github.com/docs/). Signed-off-by: Brian <[email protected]>
2023-10-20Add CodeQL Workflow for Code Security AnalysisBrian
Add CodeQL Workflow for Code Security Analysis This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats. We added a new CodeQL workflow file (.github/workflows/codeql.yml) that - Runs on every pull request (functionality to run on every push to main branches is included as a comment for convenience). - Runs daily. - Excludes queries with a high false positive rate or low-severity findings. - Does not display results for git submodules, focusing only on our own codebase. Testing: To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code. Deployment: Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps: 1. Under the repository name, click on the Security tab. 2. In the left sidebar, click Code scanning alerts. Additional Information: - You can further customize the workflow to adapt to your specific needs by modifying the workflow file. - For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation (https://codeql.github.com/ and https://codeql.github.com/docs/). Signed-off-by: Brian <[email protected]>
2023-10-18Add CodeQL Workflow for Code Security AnalysisBrian
Add CodeQL Workflow for Code Security Analysis This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats. We added a new CodeQL workflow file (.github/workflows/codeql.yml) that - Runs on every pull request (functionality to run on every push to main branches is included as a comment for convenience). - Runs daily. - Excludes queries with a high false positive rate or low-severity findings. - Does not display results for git submodules, focusing only on our own codebase. Testing: To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code. Deployment: Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps: 1. Under the repository name, click on the Security tab. 2. In the left sidebar, click Code scanning alerts. Additional Information: - You can further customize the workflow to adapt to your specific needs by modifying the workflow file. - For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation (https://codeql.github.com/ and https://codeql.github.com/docs/). Signed-off-by: Brian <[email protected]>
2023-10-11Add CodeQL Workflow for Code Security AnalysisBrian
Add CodeQL Workflow for Code Security Analysis This pull request introduces a CodeQL workflow to enhance the security analysis of our repository. CodeQL is a powerful static analysis tool that helps identify and mitigate security vulnerabilities in our codebase. By integrating this workflow into our GitHub Actions, we can proactively identify and address potential issues before they become security threats. We added a new CodeQL workflow file (.github/workflows/codeql.yml) that - Runs on every push and pull request to the main branch. - Excludes queries with a high false positive rate or low-severity findings. - Does not display results for third-party code, focusing only on our own codebase. Testing: To validate the functionality of this workflow, we have run several test scans on the codebase and reviewed the results. The workflow successfully compiles the project, identifies issues, and provides actionable insights while reducing noise by excluding certain queries and third-party code. Deployment: Once this pull request is merged, the CodeQL workflow will be active and automatically run on every push and pull request to the main branch. To view the results of these code scans, please follow these steps: 1. Under the repository name, click on the Security tab. 2. In the left sidebar, click Code scanning alerts. Additional Information: - You can further customize the workflow to adapt to your specific needs by modifying the workflow file. - For more information on CodeQL and how to interpret its results, refer to the GitHub documentation and the CodeQL documentation. Signed-off-by: Brian <[email protected]>
2023-09-28improve esp32 ci, build esp32 with -DDMAX3421_HOST=1 for max3421 testinghathach
revert change in hcd.h
2023-09-27Merge branch 'master' into add-in_isr-to-hcd_int_hanlderHa Thach
2023-09-27fix build with lpc54hathach
2023-09-19fix build and add u5 to cihathach
2023-09-11update readme to include max3421 supporthathach
2023-09-07add cmake support for samd21.hathach
update ci cmake
2023-09-07add samd51 to cmakehathach
2023-08-14add iar support for lpc43, add lpcxpresso43s67 to hil farmhathach
2023-08-09rename hitl to hilhathach
2023-08-09update hil test and json (remove troublesome lpc54608), run hil test on ci ↵hathach
with IAR build
2023-08-04add usb serial for hw l412 testhathach
2023-08-04add cmake for all board in stm32f4. fix build, also move ci for f4 from ↵hathach
makefile to cmake
2023-08-04Merge branch 'master' into enhance-bsphathach
2023-08-03add lpc43 familyhathach
2023-08-01enable flto for ra makefilehathach
- remove ra from ci make build since it is already in cmake ci
2023-07-24add lpc40 to cmakehathach
2023-07-01remove left-over build_armhathach
2023-07-01rework ra buildhathach
2023-06-25update hw test l4hathach
2023-06-25fix ci with lpc55 and kl, move hw test l4 to cmake iarhathach
2023-06-25run ci with -DCMAKE_BUILD_TYPE=MinSizeRelhathach
2023-06-24more cmake less makehathach
2023-06-24move some family ci make to cmakehathach
2023-06-24move all IAR to cmakehathach
2023-06-24add cmake for f0, f1hathach
2023-06-24allow to skip CPU_COREhathach
2023-06-24rename to kinetis_k32l2, rename OPT_MCU_KINETIS_K32 to OPT_MCU_KINETIS_K32Lhathach
2023-06-16correct cmake iar buildhathach
2023-06-16update h7 to cmake, and move iar build to cmakehathach
2023-06-16fix build warningshathach
2023-06-15fix ci with win/machathach
2023-06-02fix cihathach
2023-06-02build g0 g4 iar cmakehathach
2023-06-02cmake refactorhathach
2023-06-01add freertosconfig for g0, add cmake stlink, add g0 to cmake cihathach
2023-05-26fix artifacts locationhathach
2023-05-26more testhathach
2023-05-26retry hw testhathach
2023-05-26forgot to move hw testhathach
2023-05-26move lpc18 and rp2040 to cmake workflow since rp2040 often failed randomly ↵hathach
with make
2023-05-26update deps, rename kinetis_k32 to k32lhathach
2023-05-26use get_deps.pyhathach
2023-05-25fix issue with ftdi host driver with status byteshathach
add workflow_dispatch to all ci workflow
2023-05-25add workflow_dispatch for manual triggerhathach
2023-05-25update get_deps.py to support geting family as argumenthathach
2023-05-23Enhance chipidea (#2075)Ha Thach
* update chipidea dcd, remove manual ep_count and use DCCPARAMS to get number of endpoint instead * add dcd dcache for chipidea * add cmake for lpc18 * add makefile build for mcx * use fork of mcu sdk * fix ci build with nrf * flash rp2040 with openocd
generated by cgit v1.3.1 (git 2.54.0) at 2026-08-16 03:44:47 +0000