Coding Style Guidline.rst
Created a unified version of the Coding Style Guidelines
Extracted rules from various pandas website information as well as submission scripts that verify style requirements
Work in progress

- [x] closes #33851
- [ ] tests added / passed
- [ ] passes `black pandas`
- [ ] passes `git diff upstream/master -u -- "*.py" | flake8 --diff`
- [ ] whatsnew entry

This just duplicates what is already on the docs right? If so I think can just update the existing contributing guide with links rather than a new file with copied content > 
> 
> This just duplicates what is already on the docs right? If so I think can just update the existing contributing guide with links rather than a new file with copied content

This doesn't just copy what is in the docs. 

This is just the start of the doc and I did pull information scattered in multiple locations about coding guidelines. I also started to pull out checks that are done in the script that check for coding guidelines that are not described anywhere. 

If this document becomes more robust it think that it would be a useful tool for the OSS project. I am also unsure of how to fix the CI/Checks error. It is saying there is a trailing white space after all my lines which do no show up in my IDE @WillAyd I'll trim those out and resubmit, thank you for your help!  @WillAyd I have updated those sections. Let me know if there is anything else that I could research/add @WillAyd I am also unsure of how to get past the CI / Checks portion of the pull request. It is saying there is a trailing white space after every line but in my IDE this is not there. The section on `repr` can probably go, since we mostly use fstrings now. @Stockfoot still active? If so can you simplify and address comments? @WillAyd I am still around.
I am just unsure of how to proceed. The CI/Check seems to fail no matter what I do.
I have made all the changes that were previously suggested. The only one I need to address is the most recent with @jbrockmendel 
> The section on repr can probably go, since we mostly use fstrings now.

 This pull request is stale because it has been open for thirty days with no activity. Please update or respond to this comment if you're still interested in working on this. @arw2019 I am interested in continuing. I have addressed the comments but no one has ever responded back to my question on how to proceed and actually get a pull request going. 

Every time I try and submit it will no pass CI / Checks and am unsure how to proceed...

![image](https://user-images.githubusercontent.com/36280534/98286417-37007e00-1f61-11eb-9bc5-4636207c2abc.png)


 Can you merge master again and I'll take a look (output from the last build is no longer available for inspection). Some failures are random but we want to make sure otherwise will have to address

Also I might be wrong but I don't think you responded to https://github.com/pandas-dev/pandas/pull/34608/files#r440389770 Closing for now. @Stockfoot let us know whenever you'd like to pick this up and we'll reopen