Conversation
Collaborator
Author
|
Seems to run the tests just fine! If this is merged, I would recommend using the "squash and merge" function. There's quite a lot of test commits here. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR adds some basic github actions which effect the master and dev branches.
Action (1) On PR, the test suite is run before merging.
Action (2) On a merged PR or push to repo, the documentation is regenerated.
Github actions is a little complicated but very powerful. I imagine this will not be the first iteration of actions we use. I think the best way we can stress test these actions is to use them. This PR also adds a "requirements.txt" file. This is necessary for github actions to properly run our tests but also generally nice to have.