Management suddenly decide to push for an early go-live for a product being worked on by another dev team in the company. As a result we are pulled in to help and get extra tasks loaded onto our sprint.
My co-worker pulled an all nighter to get the extra work done.
I emailed the project manager to remove items from my sprint to make space for the new work.

Am I lazy, or smart?

If your entire going to reach the sprint goal aka complete all of the PBI's it's completely realistic to refocus the sprint on something achievable...

They've overcommitted you in the first place, you're wise to at least try and push back. If they don't let you remove items then they should realise when you don't complete everything

Adding tasks to a sprint mid-run?
push back is a must. did you even estimate the effort for those tasks? or were they added without your consent?

Oh adding new tasks in mid sprint but the deadline will not move? Request for an overtime with pay 👌

@magicMirror I did break my requirements down into tasks with labor estimates, and requested other tasks to the same value be removed, and that was done without complaint.

I'm just concerned that I will look lazy in the eyes of management compared to the developer that chose to work all night, never mind that his code will probably sloppy as hell today cos he's exhausted.

@cjbatz I wouldn't worry. You don't want to set that expectation.

@cjbatz The other dev made a big mistake, and will probably fail to deliver both sides of the sprint at the same time.
But sometimes, it is ok to fail, but look like you put in the extra effort. I always measure by delivery - but others don't. Make sure not to fall into this trap: frame it as a proffesional/sprint delivery problem, and ask the "team" what is the correct way.

There are no fukin superheros in agile.