You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A repository is expected to contain at least two branches: master and develop. Should we make VersionForRepositoryFinder throw if
At least one of them doesn't exist?
The branch develop didn't initially branch off of master?
The above post use some lax wording regarding the constraints (eg. A feature branch may branch off from develop). Should we enforce such constraints
Make HotfixVersionFinder throw if the examined branch doesn't branch off of master?
Make ReleaseVersionFinder and FeatureVersionFinder throw if the examined branch doesn't branch off of develop?
The LibGitExtensions.GetBranch() performs a fetch from the first remote found if a specified branch cannot be found locally. Why do we need such behavior? In which context/environment is that triggered?
The text was updated successfully, but these errors were encountered:
According to http://nvie.com/posts/a-successful-git-branching-model/
A repository is expected to contain at least two branches:
master
anddevelop
. Should we makeVersionForRepositoryFinder
throw ifdevelop
didn't initially branch off ofmaster
?The above post use some lax wording regarding the constraints (eg. A feature branch may branch off from develop). Should we enforce such constraints
HotfixVersionFinder
throw if the examined branch doesn't branch off ofmaster
?ReleaseVersionFinder
andFeatureVersionFinder
throw if the examined branch doesn't branch off ofdevelop
?The
LibGitExtensions.GetBranch()
performs a fetch from the first remote found if a specified branch cannot be found locally. Why do we need such behavior? In which context/environment is that triggered?The text was updated successfully, but these errors were encountered: