title: Seeking solution to maintain stable codeline in Git using feature branches
body: <p>Seeking a solution to this problem. </p>
  
  <p>We work with Git on one large feature branch off develop branch. Team prefers this way claiming individual feature branches would limit developers working similar issues and who need to share code changes.</p>
  
  <p>At end of sprint, feature\integration branch is merged to develop branch (the Configuration managed controlled branch).</p>
  
  <p>My problem is develop branch always contains some half-baked code each release.  Some issues can't finish during sprint, yet changes were committed; and yet those that are finished may depend on the half-baked code to build successfully. Is it even possible to keep a stable, tested, peer-reviewed main codeline? </p>