Branch pruning and switch to PRs from a fork #45
Labels
No labels
bug
duplicate
enhancement
prospective
question
todo
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: glen/dyna3#45
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I haven't been pruning branches in merges because every time I have asked about it, the conclusion we have reached is not to prune. The outcome is the branch structure in the main repo has become very cluttered. So please
(a) fork the repo to work on it
(b) prune any branches in the main repo that you're not certain we have some plausible use for
(c) Do whatever you like with the branches in your fork ;-) (that's the real reason to fork)
(d) Please issue PRs from a fork going forward.
Thanks so much! You can close this issue once you have completed (b).
Here's a preview of what I'd prune and what I'd keep. Let me know if you'd like any changes! If we regret pruning a branch, will recovering it be as easy as pushing it again from my fork?
Prune
Merged into
main
normalize-by-contracting
: #43uniform-projection
: #34tangent-space
: #29select-in-display
: #25cargo-examples_on_main
: #24element-serial
: #22outline-cleanup_on_main
: #19engine-integration
: #15app-proto
: #14engine-proto
: #13Superseded by a branch that was merged into
main
cargo-examples
: rebased ontomain
and merged in #24outline-cleanup
: rebased onto main and merged in #19gram
: extended toengine-proto
and merged in #13Unlikely to come in handy
macaulay2
: A quickly-abandoned effort to use Macaulay2 in the algebraic solver prototypeKeep
kaleidocycle-example
: Soon to be rebased and mergedoutline-update-fix
: superseded by a new approach, but kept in case we reconsider, as described herelang-trials
: Usefully records our explorations of candidate programming environmentsseed-problem
: Solves a subtle reproducibility problem in the algebraic engine prototypeLooks perfect and yes restoring is that easy, if you have kept a branch in your fork. Thanks! (And don't feel obliged to keep lots of branches in your fork either, in practice I have never wanted the intermediate stages of a merged branch.)
Done!