-
Notifications
You must be signed in to change notification settings - Fork 5
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
Refactoring #199
base: master
Are you sure you want to change the base?
Refactoring #199
Conversation
Black Formatter caused a lot of the line changes. The other 4 commits are the ones that need review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there's something other than auto refactoring you want looked at you should put it into a separate PR.
I reverted the auto-refactoring |
I see the reversion commits, and yet there are still 26 files changed, and all the commit titles still include "refactor". Did you do all that refactoring by hand? (Impressive :-) Did you test your changes in any way? Normally, a refactor doesn't need (as much) testing because the changes aren't intended to be semantic, but for an interpreted language you can't use "see, it compiles" as proof you didn't break anything. |
I'm not sure how to test it. The instructions on the readme don't seem to work |
There are a bunch of different configurations, depending on whether you are connecting to a dev board or flat sat via UHF or USB. We can meet next week to try it out (although it's a busy week with MCR etc). |
It says you merged 'master' into 'Refactoring', which, unfortunately, is backwards :-/ |
If you're busy this week, we could test it next week. Also I merged main into refactoring so that the code is up to date with the main branch. There was a merge conflict I wanted to resolve and it makes merging back into main a lot easier |
It's true you can't merge your branch if there are conflicts. Unfortunately, merging main into the branch messes up the history. Fortunately, we are unlikely to have to use the history to find any regressions. We're trying to follow the same processes you're going to have to follow when you get to industry. I can help you resolve the conflicts if it happens again. |
No description provided.