Home/ Questions/Q 3594454
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-18T19:42:56+00:00

New to git. A bit confused about how some of it works, conceptually. So

  • 0

New to git. A bit confused about how some of it works, conceptually.

So it sounds like, in terms of local work, its a good idea to have a branch that contains only what goes into production and another for testing out ideas, etc. which I can then merge. Is it as simple as creating those branches and then when I don’t want any recent changes to my project to be committed to the master branch, I just switch to the “testing” branch and commit/push from there? I’m just confused about the interaction between local project activity and git.

Say, for example, I add some code to my android project and save, those changes will have no effect on master repo unless I commit? And that’s the case even though, in terms of the actual local project, those changes were saved.

Am I thinking about this right? If not, set me straight?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Say, for example, I add some code to
    my android project and save, those
    changes will have no effect on master
    repo unless I commit? And that’s the
    case even though, in terms of the
    actual local project, those changes
    were saved.

    Actually they won’t change anything in the master repo until you push.
    It will change your local repo when you commit.

    It’s really up to you how you want to organize your branches (really depends on how many things you work at the same time), but you can always have those branches, commit to them and when you have something consistent, you can always create a new branch of things to merge, use cherry-pick and/or rebase -i to make it a clean serie of commits and merge/push that branch.

    • 0