DOC : Updated the comparison with spreadsheets with GroupBy
State: closed

- [x] part of #38990
- [ ] tests added / passed
- [ ] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing.html#code-standards) for how to run them
- [ ] whatsnew entry


Labels:
name: Docs
name: IO Excel
description: read_excel, to_excel

Comments:
Oh, one more thing:

- [x] Change "closes #38990" to "part of #38990" up top so the issue isn't automatically closed, since there will be remaining tasks
Also, the build failure seems unrelated to this change.
@Bhard27 - Are you interested in finishing this up? I think changes look good, can you merge master and will have another look.
> @Bhard27 - Are you interested in finishing this up? I think changes look good, can you merge master and will have another look.

Hey, I have pushed the changes you suggested. Is there anything else that needs to be done in this? Also, I don't have permission to merge this to master.
@Bhard27 - yes, can you merge the master branch into your PR branch (happy to help with further instructions if you're unfamiliar with doing this, just let me know). We like to do this to run the CI on the most recent changes with master.

> Also, I don't have permission to merge this to master.

Right, that needs to be done by a maintainer. Even maintainers shouldn't merge there own PRs ;)
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.
@Bhard27 - friendly ping, are you interested in continuing this?
> @Bhard27 - friendly ping, are you interested in continuing this?

Sorry about the inactivity. I am a little confused about merging it with master branch because I think I already pushed it in the master branch.
<img width="265" alt="Screenshot 2021-06-06 at 5 05 02 PM" src="https://user-images.githubusercontent.com/50989807/120922888-58893a00-c6e9-11eb-914a-e6791e295463.png">

@Bhard27 I think what you've screenshot is the fact that you are doing a pull request from your branch into master. This branch was last updated on February 28th, and the tests that ran were based on what this patch (which hasn't changed) and master (which _has_ changed) combined together. In general, we'd like to make sure the tests get run on a very recent copy of master, so the request here is to merge the master branch into this PR branch. Doing so will run the tests again on all the updated code.

To do this, run the command `git merge upstream/master`, then push to origin (your fork of the repo). In general you may have to resolve conflicts, but I don't believe that there will be any.
> @Bhard27 I think what you've screenshot is the fact that you are doing a pull request from your branch into master. This branch was last updated on February 28th, and the tests that ran were based on what this patch (which hasn't changed) and master (which _has_ changed) combined together. In general, we'd like to make sure the tests get run on a very recent copy of master, so the request here is to merge the master branch into this PR branch. Doing so will run the tests again on all the updated code.
> 
> To do this, run the command `git merge upstream/master`, then push to origin (your fork of the repo). In general you may have to resolve conflicts, but I don't believe that there will be any.

Oh, Thanks a lot for the explanation. I totally understand why we need to merge it again and run the tests. I will do that ASAP
@Bhard27 - closing this as stale, but reply here if you are interested in continuing and can reopen.