Thanks !

You did commit all your .idea file though. See here on how to create a global git ignore file, and add .idea to it.

Then we can walk through how to squash your history for those files to not be added to repo.

If you code work on Python 3.7 at the REPL you should see the following:

In [1]: import warnings
   ...: def foo():
   ...:     warnings.warn('OH Noooo', DeprecationWarning)
   ...:

In [2]: foo()
/Users/bussonniermatthias/anaconda/bin/ipython:3: DeprecationWarning: OH Noooo
  __requires__ = 'ipython'

Good job, and thanks @eamanu for the review !

Thank you @Carreau ! I'm new to pull requests, so thank you for sending me this tutorial.

I'll come back with changes in a bit.

Feel free to ask if you want more guidance. I'll stay short on purpose – to gitve you the opportunity to figure it out by yourself –  but I can give you detailed instructions if needed.

Thank you @Carreau !
What I did so far:

1. created a global .gitignore_global
2. added ./idea to ir

It wasn't working properly, though, because I had to remove the files from git's tracking. I removed them with git rm -rf .idea and it said that the files inside the folder were succesfully removed. But whenever I tried to commit and push, the repository was already up-to-date.

3. so I decided to exclude the ./idea folder

and it worked.

Does this sound right? Is there a better way to do it?

Thanks

It's good, let me show you how to rewrite the history to have only one clean commit and not have the intermediate .idea files in history.

We'll rebase interactive (-i) and squash (s) the last two commits

$ git rebase -i HEAD~3
<vim open if you haven't set $EDITOR>
<press i and Edit the second and third line, replace "pick" by "s">
<press ESC : w q Enter>
< write your new commit message>

Now you can force push.

Here is it as a gif.

If it's too complicated I can do that for you.

Great!

Hi there @Carreau !

Thank you for the help, I believe I did successfully what you asked for. This GIF is great!

What are the next steps now? should we do some more testing?

Great!

Than you @eamanu !

What are the next steps now? should we do some more testing?

No more step for this issue that you. For this specific issue I don't think more testing is necessary I'll just update 11333 so that once we drop 3.6 the code can actually be removed.... but that will take a couple of years.

Good job!

Good job!

@Carreau thank you! Now I'm looking for more issues to work on, do you have any suggestions?

do you have any suggestions?

Not particularly, I'll have to go through and figure out if issues are easy or hard.

You can try to go through the list of what is needed for 7.1 release some of them have been fixed and just need to be closed.

You should be able to also apply a subset of labels to issues by gently asking our bot like so:

@meeseeksdev tag hacktoberfest

I'll try to mark a few issue as "good first issue" and/or "help wanted"