I’m the only person using the repo. The link you mentioned talks about fetching from the remote. Does it mean pulling? That, presumably, will pull those two newer commits back down again which I don’t want to do.
On Desktop, open terminal in Wappler and do a force push: git push -f.
This will remove the higher commits in remote and bring it back to the commit you want.
On laptop, switch to another branch, then remove master from local, and then checkout master again.
If you don’t have another branch, create one just for this purpose, then delete after switching to master.
If you do not wish to create a branch, delete the project folder from your machine and do a fresh clone.
Hi again @sid. I was thinking I was using username/password but I now realise I used oauth from my browser to give Wappler access. Terminal in Wappler isn’t letting me do the forced push, though (see above).
I have never had a problem with running commands on terminal.
You can try the same thing on source tree. They have a Git terminal option.
Maybe you need to authenticate this Git repo via browser access or personal access token instead of username password that you might have used.
Generally, the access given from Wappler is enough for system Git to get access… But it could that you are using some other option in the Git installation. Windows/Mac could be a cause of issue as well.
I’ve managed to sort it by deleting my repo at Github, recreating it and then pushing my local one to it. Really simple solution that just works. Perhaps not as tidy as being able to do it with the existing repo but not a big deal.
Posting this in case someone else is in a similar position.