-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Branch cleanup #1397
Comments
@fredgalvao all of the branches I've put checkmarks beside can be cleaned up. I want to leave the following around:
Feel free to start cleaning and thanks for supporting this project! |
Should I leave |
@fredgalvao nah, I think the work will need to be restarted so just having Holly's commit in |
Yep, just verified and the code on that |
Seems good enough for now! (now to create a few new branches/issues for crazy ideas I have for the api...) |
@fredgalvao at some point the two of us and @jcesarmobile should get together for a roadmap planning session. Rough schedule is:
|
@macdonst I'd love to have a chance at sharing my opinion on some of those topics. |
This thread has been automatically locked. |
Expected Behaviour
Clean and consise branch timeline/tree.
Actual Behaviour
We have a ton of branches that outlived their yet-to-be-seen importance.
Reproduce Scenario (including but not limited to)
Steps to Reproduce
Click here
Shall we do a cleanup on those branches?, that:
have already been merged
have no diff
from
master (most of them have diffto
master, as they're outdated)have a diff
from
master but that diff has already been cherry-picked to masterwho knows
cocoapod_support
branch.Pushy.me
or Amazon. IMO this should be considered and not deleted right away. [WIP] Amazon Device Message Support #822v2.0.x-rebase
master
The text was updated successfully, but these errors were encountered: