-
Notifications
You must be signed in to change notification settings - Fork 11
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
Fix/complete-natspec-issue-17 #322
Conversation
I think @Rubilmax you must update some of your PRs to point to this one right? |
Why did you change the branch? Couldn't we continue working on the other? |
The other one was polluted with many commits (idk really know why). I suggested a rebase but @Jean-Grimal opted for this solution which works also. |
Indeed it also works, but it nullifies the work I did to base my work on the previous branch, so I can't support this I'll merge this branch into the previous branch to see how it looks and if it looks fine I prefer to still work on the previous branch, which avoids to duplicate my work |
See #302: what's the issue? If there's none, pls close this PR and move back to the previous branch which I just updated with this work |
It looks fine. Actually I just didn't have enough git skills, that's why I created a new branch. |
The issue was before, perhaps a missing merge? see below |
Alright, then it's all sorted out! |
Fixes https://github.com/cantinasec/review-morpho-blue-1/issues/17