Continuous Integration (5/10)
Good progress, looks like the branch protection rules are not on, -5, easy fix, see the guide posted in the Discord questions channel for D3
Setup Continuous Integration for your team’s Github repo using Github Actions.
Here relevant tutorials for Github Actions
Here is a repo from last year with CI correctly set up, and a document describing their setup
When any commit is pushed to main or a pull request on main is made, all the tests should be run and any failing tests should cause the push to be rejected or show that the pull request does not pass the test
Survive Dr. Greg’s Nefarious Commit!
Dr. Greg will mangle your code and push it to your main branch
If the push is not rejected by your continuous integration tests, -10
If the push is not rejected, your team will also have to deal with getting rid of Dr. Greg’s Nefarious Commit.
If the push is rejected, Dr. Greg will make a pull request on your main and check that it shows in the pull request that the tests are failing (e.g. the place the red X or green check mark shows up like in your web textbook assignments)
Who knows when this sneaky doctor will strike again!?!?
Dr. Greg is just doing the above. There are no "github specific" malicious behaviors like changing permissions on your repository that your app's tests should detect.
Continuous Integration (5/10) Good progress, looks like the branch protection rules are not on, -5, easy fix, see the guide posted in the Discord questions channel for D3 Setup Continuous Integration for your team’s Github repo using Github Actions. Here relevant tutorials for Github Actions Here is a repo from last year with CI correctly set up, and a document describing their setup When any commit is pushed to main or a pull request on main is made, all the tests should be run and any failing tests should cause the push to be rejected or show that the pull request does not pass the test Survive Dr. Greg’s Nefarious Commit! Dr. Greg will mangle your code and push it to your main branch If the push is not rejected by your continuous integration tests, -10 If the push is not rejected, your team will also have to deal with getting rid of Dr. Greg’s Nefarious Commit. If the push is rejected, Dr. Greg will make a pull request on your main and check that it shows in the pull request that the tests are failing (e.g. the place the red X or green check mark shows up like in your web textbook assignments)
Who knows when this sneaky doctor will strike again!?!?
Dr. Greg is just doing the above. There are no "github specific" malicious behaviors like changing permissions on your repository that your app's tests should detect.