Commit d627ef0b authored by Samuel Taggart's avatar Samuel Taggart
Browse files


parent aaf0f84e
......@@ -14,5 +14,4 @@ Manual testing:
There is a folder called "code for testing" in the 1-cleanup branch. Once that gets merged in, it has a project with a simple actor that uses all 3 types of messages, so you can run the scripting on that and look at the results as a quick sanity check. It's not a very thorough test, but its the best I came up with.
Contribution Guidelines:
For now, just wait until I finish the cleanup branch and merge it back into master. It will save you a lot of headache.
After that, just simply fork it, make your changes and submit a merge request into master.
For now, just simply fork it, make your changes. Before you submit a merge request into master, run the vi analyzer tests. The results don't have to be perfect (I don't have the parameters tweaked exactly the way I want them yet), but most tests should pass.
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment