As A VA Notify Engineer
I want to have a clean git environment
So that there is less confusion
The API currently has 77 branches and many of them appear stale. This can cause confusion and delay. Remove stale branches. Create tickets to investigate branches that appear to still have a use if necessary. Some may already have issues they are attached to. Some are an unknown such as the static-assets branch having protections.
Checklist
[ ] Delete branches that appear to have no purpose
[ ] If there is any question at all, do not delete it
[ ] Questionable tickets either need an issue update, have an issue created, or discussed with @k-macmillan
Updates to existing issues may include something such as, "Marked as potentially useful/necessary, leaving the branch open".
k-macmillan
commented
1 month ago
Value Statement
As A VA Notify Engineer I want to have a clean git environment So that there is less confusion
The API currently has 77 branches and many of them appear stale. This can cause confusion and delay. Remove stale branches. Create tickets to investigate branches that appear to still have a use if necessary. Some may already have issues they are attached to. Some are an unknown such as the
static-assetsbranch having protections.Checklist
Updates to existing issues may include something such as, "Marked as potentially useful/necessary, leaving the branch open".
Additional Info/Resources
Out of Scope