Migrating from Travis CI to GitHub Actions

GRNsight Migration to Github Actions

Review

The goal is to transition from Travis CI to GitHub Actions. This will automate the continuous integration (Travis CI) process in a more integrated and efficient way, directly within GitHub.

Set up steps

1. In GRNsight, create a new folder. This is where GitHub Actions will look for files to run.

• New folder: “.github/workflows/ci.yml” where we will define what our CI (continuous integration) process will do.

2. Write the workflow! (this tells GitHub actions what to do)

• In this file, you’ll write an instructions/workflow file for what GitHub Actions should do when certain events happen (like when you push code). For example, you can tell it to do :

             - Check out your code. 
  
             - Install any necessary software (like Node.js or Python). 
  
             - Run the tests
  
             - Test the workflow 
  

2. Once you commit this file, GitHub will automatically start running your tests when you push code or open pull requests. You can check the results in the Actions tab of your repository.

Final Step

3. Remove CI Files -- After confirming everything works in GitHub Actions, you can remove the files and settings related to your old CI system.