For further actions, you may consider blocking this person and/or reporting abuse
Read next

"Unlocking AI Potential: The Power of Thermodynamic Computing and Quantum Noise Control"
Gilles Hamelink -

explica brevemente que es c# ?
Ricardo Torres -

"Unlocking Cross-Lingual Semantic Search: Insights & Innovations Revealed!"
Gilles Hamelink -

explica brevemente que es c# ?
Ricardo Torres -
Top comments (1)
GitHub's pull requests can be updated by pushing new commits to the existing branch. This is a deliberate design decision allowing PRs to be incrementally improved.
The solution is to push the changes you wish to be considered separately to a different branch and to open a new PR from that branch.
Source: stackoverflow.com/questions/344807...