Set up a GitHub Actions workflow for Continuous Integration (CI) that includes running Valgrind for memory checking. This issue aims to track the process of configuring the CI workflow and addressing any issues encountered during the setup.
Requirements:
[ ] Create a GitHub Actions workflow YAML file.
[ ] Configure the workflow to build the C project.
[ ] Run Valgrind on the project to check for memory errors and leaks.
[ ] Report the Valgrind results as part of the CI workflow.
Steps:
Created a new GitHub Actions workflow YAML file.
Configured the workflow to build the C project.
Build the project
Run Valgrind on the project.
Expected Outcome:
Upon successful implementation of this GitHub Actions workflow, the CI system should automatically build the project and run Valgrind during every push or pull request. Any memory issues or leaks should be reported as part of the CI results.
Set up a GitHub Actions workflow for Continuous Integration (CI) that includes running Valgrind for memory checking. This issue aims to track the process of configuring the CI workflow and addressing any issues encountered during the setup.
Requirements:
Steps:
Expected Outcome:
Upon successful implementation of this GitHub Actions workflow, the CI system should automatically build the project and run Valgrind during every push or pull request. Any memory issues or leaks should be reported as part of the CI results.