-
Notifications
You must be signed in to change notification settings - Fork 666
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
replaced atoms.coordinates() with atoms.positions (Issue #3467) #3477
Conversation
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.
- Please change: .positions is an attibute not a method.
- Please remove the changes regarding units. We want to do 1 PR addressing 1 issue to keep things simple.
I approved running the tests – sorry, that's a current security measure. Please feel free to ping me @orbeckst if something is not moving along.
ohh sorry I am still new to github and python. I messed it up. |
Codecov Report
@@ Coverage Diff @@
## develop #3477 +/- ##
===========================================
+ Coverage 90.15% 93.75% +3.59%
===========================================
Files 176 176
Lines 23169 23169
Branches 3291 3297 +6
===========================================
+ Hits 20889 21723 +834
+ Misses 2280 1395 -885
- Partials 0 51 +51
Continue to review full report at Codecov.
|
@orbeckst I mailed you my issue. It'd be great if you could help me out |
@pranjii it's usually easier, faster and helps later viewers if you discuss problems here on the issue -- then all developers can pitch in and help. |
As I said I am new to github so I do not know the norms and I apologise for the troubles. I was not aware of how github worked and made changes to the already committed code unaware that any changes I made to my branch will also be made in the PR. So how do I reverse these changes keeping in mind that I made a small change in the code directly through github? Should I just close my pull request? |
Hi @pranjii , don't worry – you're fine!! There was no need to delete anything. I would have asked you to
It's totally normal that you will change and rewrite the code in the PR in response to comments. It's actually really good to see your code so that we can comment early. In short: you did everything correctly! |
@orbeckst thank u. I have closed this PR and will change the recommend things ASAP for a new PR and guess will dive a little bit deeper into git and github |
Sure. Don't worry, learning the whole pull request/review workflow takes some time. Ask us before you delete anything, we can typically give guidance. Just be aware that we might not always be able to immediately respond — we are all pretty busy an it can sometimes take a day. As @lilyminium said, we discuss all issues in public. We also follow our Code of Conduct in conducting all these discussions respectfully. |
Fixes #3467
Changes made in this Pull Request:
PR Checklist