Answer the question
In order to leave comments, you need to log in
How to organize work with GIT for one person (details inside)?
Good afternoon friends. I have been working with GIT not so long ago, and it’s more interesting to commit, pull and push, I didn’t use anything (there was no need). Now I want to delve into the study, besides, there is a certain need for the organization of work.
There is a project, you have to test it on the server, there is no such possibility on the working machine. Therefore, each code change must be placed on the server. The project gets to the server via git pull from the repository (the repository is configured on the same server). On another machine, there is already a production version, the data also flies there from the main repository via pull. The problem is that I don't want to push a ton of commits to the prod server, there's no point in that. Tell me, what do you do in such cases? There was an idea to make two repositories, to throw "trash" with your branches into one, for work and instant tests, to throw the necessary commits into the second, which will then be uploaded to production.
Can eat more graceful and competent method?
Answer the question
In order to leave comments, you need to log in
I'm on ubuntu. Using sshfs I mount a folder from the server. I'm working in the Sublime Text editor with files inside this folder (in the editor it's created as a project folder). Work with git goes through ssh in the console.
In principle, according to a similar scheme, you can work from any computer. It's just that on the same windows you have to set up file synchronization via sftp (because it turned out to be the easiest way to use the FileZilla client, the client built into SublimeText turned out to be glitchy and had to be abandoned).
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question