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
I want to maintain a clean GitHub repository with a clear branch structure
so that I easily identify the active feature branches and release branches, whilst deleting stale/merged branches
Additional context
It's safe to delete inactive branches after they were merged into develop/main
The code will not be lost and is still considered for grading, as the history/commits are visible in the develop branch
Statement by Thomas:
Hi,
there are basically two scenarios you should consider:
You have merged all changes of your feature branch to your main branch. In this case there is no relevant work left in the feature branch because it can be found in the main branch. You can delete these branches.
There are some unmerged changes on your feature branch. In this case there is relevant work which would be lost by deleting the branch. In this case don't delete the branch.
Cheers,
Thomas
Acceptance Criteria
All unused/stale/merged branches are deleted
The branch structure is in a clean state
Branches that should NOT be deleted
develop
merge/core-develop-cone
merge/to-core
other active branches
Definition of Done
Test cases have been created and are running successfully
Documentation for the new component was added
Github Actions are running without errors
The text was updated successfully, but these errors were encountered:
User Story
Additional context
Acceptance Criteria
develop
merge/core-develop-cone
merge/to-core
Definition of Done
The text was updated successfully, but these errors were encountered: