-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
bank-account: implement exercise #730
Comments
I'd like to take a look at this one. |
@aes421 that is awesome, good luck! |
Hey @m-a-ge I read up on rebasing. Do you want me to squash all my commits into one? |
@aes421 that would be great. |
@m-a-ge Did you mean unwanted commits? |
@m-a-ge Got everything cleaned up. What should I do next to finish off the pull request? |
@aes421 I (or someone else) will review it once again to make sure everything is Ok and merge it. |
No problem, I understand. Thanks! |
This issue has been automatically marked as |
@cmccandless This issue was resolved in #1260. Please close it. |
Closed in #1260 |
There are exercises that are not yet implemented in Python track (the full list of them - #417 (comment)).
You can help us change this situation by implementing this one. Ref #417
The guide "Implement an exercise from specification" will help you succeed.
If you still have questions, I encourage you to ask them before starting working on the issue.
I also suggest claiming the issue by creating an empty PR as stated here
Please note that there are some special 'closing issue' keywords that you can put in description of your PR and Github will take care of closing the corresponding issue automatically after merge.
This simple thing helps us a lot, and makes our life a bit easier
The text was updated successfully, but these errors were encountered: