I’m not totally clear on why some changes I make get committed automatically to a forked repl while others require me to enter a commit message in the Git tab in order to have them ‘committed’ to the app.
1 Like
Replit’s tool should never automatically commit (push) back to the Github repo. I am relatively new to Git, but what I think happens with the git tool is:
-
if Replit can work out a commit message from your change then it adds one. But it then simply marks it as a uncommitted, ready for you to push
-
if Replit can’t work out a commit message from your change then it asks you for one. But again, it then simply marks it as a uncommitted, ready for you to push
I’d love to hear a better explanation from a git pro.
Bottom line though, you should always remain in charge of doing the actual pushes.
Thank you @Gipity-Steve . Let me clarify that I’m using the Project feature in Replit in which changes made to a fork appear as either Committed or Uncommitted changes prior to Merging with the main repl in the Project tab. So Replit is not pushing unwanted changes to the main repl. But there is a distinction made between committed changes vs uncommitted changes prior to the final merge with the main repl.
I think what you’re saying (correct me if I’m misunderstanding) is that Replit may be inferring a commit message from my chats for some changes while it is not inferring a commit message for others.
1 Like
Ah, I’m really sorry, I didn’t realise you were using Projects - I’ve never used that. I thought this was simply the Git tool for your own direct github repos. 'fraid I’m not sure in that case.
I responded, in chat, to the last set of uncommitted changes. I said “it looks like everything worked great”….a few seconds later the uncommitted changes were committed. So perhaps that is exactly what Replit is doing. It is looking for feedback that qualifies as a commit message. I’ll keep an eye on this in the future.