amplify push causes local changes to be reverted instead of pushed to the cloud

[silveriordza]

I was experiencing the same issue, I updated one of my code files, saved it, invoked "amplify status" the change was detected, then "amplify push" and the changes of my file were reverted and amplify shows message "No changes, everything is up to date", so no changes were pushed to the Cloud. Later I found out that AMPLIFY maintains a copy of my code in a folder named #current-cloud-backend, and I was modifying the file there instead of modifying it in my own project folder. This is just and FYI for all my colleagues who asked similar question in the case referenced below, just look you are not modifying your code files on that amplify folder #current-cloud-backend, and modify it in your own project folder instead.
Cheers!
Silver.

Previous ticket referenced:
@StevenJE @Zablas I've experienced this exact same issue when I'm modifying files in amplify/#current-cloud-backend/.. directories instead of files in amplify/backend/... :) Could you please check again if that's not the case?

Originally posted by @kaustavghosh06 in #5097 (comment)

[josefaidt]

Hey @silveriordza 👋 thanks for raising this and apologies for the delay! Would you mind porting this over to our bug template? This will help us gather additional context around the issue you are experiencing 🙂

[josefaidt]

Closing due to inactivity

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.