Win a copy of Python Continuous Integration and Delivery this week in the Python forum!
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Paul Clapham
  • Jeanne Boyarsky
Sheriffs:
  • Devaka Cooray
  • Junilu Lacar
  • Tim Cooke
Saloon Keepers:
  • Tim Moores
  • Ron McLeod
  • Tim Holloway
  • Claude Moore
  • Stephan van Hulst
Bartenders:
  • Winston Gutkowski
  • Carey Brown
  • Frits Walraven

Changes made on branch using git impacts the original branch?  RSS feed

 
Ranch Hand
Posts: 252
3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I'm wondering what I'm doing wrong here.  I've made a copy of my develop branch called task_2219  by using git checkout -b task_2219.   I made changes to the new branch but then decided I wanted to go back to the develop branch.  I did the git checkout develop and I see all the files I made changes to while on task_2219 is listed starting with an "M"

For example:
M src/main/java/com/task/RunFeatureTests.java

The changes show up to these files on the develop branch.  

Should I have stashed my changes on task_2219 before switching branches?
 
Sheriff
Posts: 4589
288
Clojure IntelliJ IDE Java
  • Likes 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
You did not commit any changes to the task_2219 branch so you're still working with local changes that do not belong to any git branch. If you're not ready to commit them, then you can stash them, otherwise commit them before switching back to the develop branch.
 
Lisa Austin
Ranch Hand
Posts: 252
3
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator

Tim Cooke wrote:You did not commit any changes to the task_2219 branch so you're still working with local changes that do not belong to any git branch. If you're not ready to commit them, then you can stash them, otherwise commit them before switching back to the develop branch.



Ah That makes sense.  Thank You.  
 
I didn't do it. You can't prove it. Nobody saw me. The sheep are lying! This tiny ad is my witness!
Become a Java guru with IntelliJ IDEA
https://www.jetbrains.com/idea/
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!