Cool. Now you should squash the commits. See: https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#squashing-commits

Oops.. I think I did something wrong..
I first wrote

$ git rebase -i HEAD~3
$ git pull origin issue_20576 (Since it was asking me to take a pull)
$ git push origin issue_20576

@anshu-khare-design try this

git reset --hard 133f73e86bd7c3114263500be2fb5090dd76b4bc

git push origin +133f73e86bd7c3114263500be2fb5090dd76b4bc^:issue_20576

git push origin 133f73e86bd7c3114263500be2fb5090dd76b4bc:issue_20576

This will close the pull request, it will have 0 commits and you can start fresh in your fork repository

Make all the changes in the code, do 1 commit and reopen pull request.

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Conflicts

Reviewers, this pull request conflicts with the following ones:

• #24230 (indexes: Stop using node internal types and locking cs_main, improve sync logic by ryanofsky)
• #24178 (p2p: Respond to getheaders if we have sufficient chainwork by sdaftuar)
• #24008 (assumeutxo: net_processing changes by jamesob)
• #23604 (Use Sock in CNode by vasild)
• #23443 (p2p: Erlay support signaling by naumenkogs)
• #22778 (net processing: Reduce resource usage for inbound block-relay-only connections by jnewbery)
• #22053 (refactor: Release cs_main before MaybeSendFeefilter by MarcoFalke)
• #21160 (net/net processing: Move tx inventory into net_processing by jnewbery)
• #20799 (net processing: Only support version 2 compact blocks by jnewbery)
• #20726 (p2p: Add DISABLETX message for negotiating block-relay-only connections by sdaftuar)
• #15606 (assumeutxo by jamesob)

If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

🐙 This pull request conflicts with the target branch and needs rebase.

_{Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft".}

@prayank23 gave some tips. Feel free to ask for help whenever needed.

Please don't open new PRs for the same change. (#24273).