Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add github actions integration #155

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

brahimrizqHireme
Copy link
Contributor

@brahimrizqHireme brahimrizqHireme commented Jul 23, 2024

Title: Add GitHub Actions Workflow for CI/CD and Code Coverage

Description

This pull request adds a GitHub Actions workflow for continuous integration and continuous deployment (CI/CD). It includes running tests with code coverage reporting using PHPUnit and Codecov.

Motivation and context

This change is required to automate the testing and deployment process, ensuring that our code is consistently tested and meets quality standards before being merged. It also provides code coverage metrics to help identify areas of the codebase that may need more thorough testing.

How has this been tested?

  • The GitHub Actions workflow has been triggered on push and pull_request events to the main branch.
  • Verified that the workflow runs PHPUnit tests and generates a code coverage report.
  • Checked that the code coverage report is successfully uploaded to Codecov.
  • Ensured that the MongoDB service is correctly set up and accessible during the tests.

Testing environment:

  • Ubuntu-latest
  • PHP 8.3
  • MongoDB 7.0

Screenshots (if appropriate)

image

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)

Checklist

Go over all the following points, and put an x in all the boxes that apply.

Please, please, please, don't send your pull request until all of the boxes are ticked. Once your pull request is created, it will trigger a build on our continuous integration server to make sure your tests and code style pass.

  • I have read the CONTRIBUTING document.
  • My pull request addresses exactly one patch/feature.
  • I have created a branch for this patch/feature.
  • Each individual commit in the pull request is meaningful.
  • I have added tests to cover my changes.
  • If my change requires a change to the documentation, I have updated it accordingly.

Additional Steps

Enable GitHub Pages:
Go to your repository's settings on GitHub.
Under the "Pages" section, set the source to gh-pages branch (or the default branch if using a different setup).
Check the GitHub Pages URL: at https://.github.io//.

@brahimrizqHireme brahimrizqHireme mentioned this pull request Jul 23, 2024
9 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant