-
Notifications
You must be signed in to change notification settings - Fork 9
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
Removing __all__ in modules #36
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.
This looks great!
However, please don't remove the .gitignore
file (mentioned in the inline comment as well).
Otherwise this would be ready to merge
After this one is done, could you make a similar change in kcidb?
.gitignore
Outdated
@@ -1,3 +0,0 @@ | |||
__pycache__ | |||
*.egg-info | |||
*.pyc |
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 do not remove this file, we need it 😁
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.
Okay
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.
Thank you :) However, this file still shows the change because the newline was removed from the last line. Could you fix that? You can just fetch the previous version of the file with something like git checkout HEAD^ -- .gitignore
, and then amend the file in the last commit with git commit --amend --no-edit .gitignore
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.
I did what you asked me to. Is it okay now?
bac8501
to
b85d816
Compare
The change looks good now, but there's a merge commit we don't need. Could you please remove it? |
Yes, I realized that and I do need help removing it |
No problem! First, let's see how your remotes are setup. Could you post the output of |
$ git remote -v |
Alright, first let's add the remote for this repo (the one you're contributing to, as opposed to your fork that your command listed). Let's name it "upstream":
You can check that this worked by running Then fetch from the remote (or "repo") that you just added:
Now you're ready to "rebase" your changes on top of what's in the "main" branch of this ("upstream") repo:
The above should complete without a problem. Then you should be able to preview the difference between this repo's main branch, and your local branch, like this:
It should output something like this:
If this is what you see (or close to, but still only one line of output), then you've done it, and are ready to force-push to your PR branch again! Please ask questions if anything is unclear, good luck 😀 |
I was able to follow your instructions. I hope it's okay now ☺ |
Yes, it's perfect now, merging! Thanks and congratulations on your first PR 🥳 |
Thank you for your guidance @spbnick 👏 👏 |
#33 Remove use of all from all modules