I’m sad cause I thought I could use the github but unfortunately I don’t know how to use it right…
This morning I tried to publish to remote server a few changes I had made to my files and there was a message about an error during the publish…
Tried a second time and got the same message.
And sadly realized that my site is not working at all… No page at all.
I tried to see what the problem is on my local files and noticed that there was a problem on my database connection file…
(C:\xampp\htdocs\stock\stock\dmxConnect\modules\Connections)
When I tried to open/edit it (with notepad), I was getting an alert that I have no permission rights for this file…
Anyway I prefer to go from a previous Git point I have that was working and have my files fixed from there (I have also kept localy my files…)
So, my question is:
How can I go to a few changed back from my git?
I don’t know about doing it inside Wappler, but if you use some other Git client you can open the project folder and then revert each commit till you reach the one you want
Maybe I don’t fully understand it but you aren’t allowed to right click that commit and “revert to this point”?
Never used it but the option is there I guess
Interestingly, the reason I said “revert the commit” is precisely because I don’t know the answer to the question you’re asking, I only know the behaviour of reverting a commit. Maybe @ franse knows the answer?
I don’t know the operation of “reset to this commit”.
But I assume the option you need is the one is two options above: “revert to this commit”.
Honestly don’t know the difference between both.
Like I said, never had the chance to use it, but I guess that it will revert the files to that commit.
I prefer to use SourceTree for this.
Revert will do what you are expecting… but state of files will be mixed.
Using ST, you get the option to “reset current branch to this commit”. On doing so, it will ask what you want to do with uncommitted files. I use HARD RESET option.
Additionally, if you want to reset the remote branch to selected commit as well… once you have done it locally, use git terminal to do force push - git push -f
Be careful though.
In the old days I worked in VAX/VMS Architecture and Assembly… Compared to using Git I found that simple. All I’ve ever managed to do with Git is mess things up. These days I have reverted to using TimeShift (a Linux backup tool). Am sure brain surgery is easier than getting to grips with Git. However it is something I would like to learn to use properly, but for now I’m scared of it.
I was scared of Git at one point too.
And I started using it only after backups and shared drives wouldn’t work any more because we had a team working on shared code - so I was sort of forced to use Git.
Git has a learning curve, but unless you start, you would remain a cave-man.
Even after 2-3 years of using Git almost every single day, I only know a handful of commands and processes - enough to get by.
I use Wappler, terminal, source tree and VSCode for managing Git stuff.
If I ever learn all Git CLI commands, just terminal and VSCode could be enough.
You could just create a dummy repo, and play around with it. That’s how I started.
CC: @Cheese
To be honest, all you had to do was take a .zip backup of your project, and then try the options we suggested like “Reset to this commit” and then see what happened, you didn’t have to wait for someone to be sure
Now i see a ray of light coming into my cave I think…
(I suspect I’m gonna try it again… I just have to study git stuff better, “branches” etc)
Thanks again brother!
GitHub’s app is not very good in my opinion. SourceTree is much better.
Only caveat with SourceTree is that it does not have ‘side-by-side’ code diff. I use Wappler for that.
