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

Chore: Add GitHub Actions Workflows for Continuous Integration #17

Merged
merged 2 commits into from
May 3, 2024

Conversation

23nosurrend
Copy link
Collaborator

What does this PR do?

This pull request introduces two new GitHub Actions workflows to automate the testing process for both push and pull request events. These workflows are essential for ensuring code quality and functionality before changes are merged into the main branch.

Description of Workflows Added

  1. Push Trigger Workflow (push.yml):

    • Trigger: Activates on any push to any branch in the repository.
    • Purpose: Ensures that every push to the repository, regardless of the branch, passes all configured tests.
    • Steps Executed:
      • Checkout the code.
      • Set up the Node.js environment.
      • Install all necessary dependencies.
      • Execute the test suite using npm run test -- --ci.
  2. Pull Request Trigger Workflow (pull_request.yml):

    • Trigger: Activates on pull requests targeted at the develop branch.
    • Purpose: Makes sure that changes in pull requests are tested against the develop branch before they are merged.
    • Steps Executed:
      • Checkout the code.
      • Set up the Node.js environment.
      • Install all necessary dependencies.
      • Execute the test suite to validate changes.

How should this be manually tested?

To verify the functionality of these workflows:

  • For Pushes: Make a commit and push it to any branch. Navigate to the "Actions" tab in GitHub and observe if the "Push Trigger Workflow" executes and passes all the steps.
  • For Pull Requests: Open a pull request to develop. Watch the "Actions" tab to see if the "Pull Request Trigger Workflow" runs and successfully completes all steps.

Any background context you want to provide?

Implementing these workflows automates our testing process, reducing the need for manual checks and helping maintain code quality through automated, consistent testing procedures. This integration into our CI/CD pipeline aligns with our objectives to improve development practices and ensure reliable software delivery.

@23nosurrend 23nosurrend requested a review from mr3nz1 May 2, 2024 07:39
@23nosurrend 23nosurrend self-assigned this May 2, 2024
@Nkbtemmy Nkbtemmy added the Need Rebase Rebase from develop label May 2, 2024
@Nkbtemmy Nkbtemmy requested a review from mr3nz1 May 2, 2024 10:25
Copy link
Member

@Nkbtemmy Nkbtemmy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just work on your commits(Squash them into one)

…dependencies

Enhance GitHub Actions setup and streamline project configuration

- Initialize GitHub Actions CI workflow for Medical App.
- Update and refactor project settings and dependencies.
- Improve CI/CD scripts and remove unnecessary npm run web step.
- Update package.json and yml configurations for better CI integration.
- Include non-interactive mode adjustments for Expo start.
- Add eslint setup for code quality enforcement.
- Consolidate and clean up GitHub workflow scripts.
- resolve conflict from Color.ts
@Irirwanirira Irirwanirira added Need Review Requires reviews and removed Need Review Requires reviews labels May 3, 2024
@23nosurrend 23nosurrend added the Need Review Requires reviews label May 3, 2024
@Nkbtemmy Nkbtemmy merged commit 2962aec into develop May 3, 2024
3 checks passed
@mr3nz1 mr3nz1 linked an issue May 3, 2024 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Need Rebase Rebase from develop Need Review Requires reviews
Projects
None yet
Development

Successfully merging this pull request may close these issues.

chore: setup github actions
4 participants