Repository navigation
BeeBranch 1.7.0
BeeBranch 1.7.0
Merges and ordinary pushes stop asking for a decision Git already made, and commit CI now finds its forge project by itself.
Changed
- Merge applies immediately: dropping a branch onto another one, or using a branch's menu, merges it at once instead of first asking for a merge strategy. The choice it used to ask is its own menu action — Fast-forward only (
--ff-only) when the target can be fast-forwarded — and a rebase keeps its single confirmation. - Plain pushes no longer ask: a push Git can send as a fast-forward goes straight to the remote. The summary bar stays for a push the remote would refuse (it moved ahead), and a force push now asks exactly once: its warning bar replaces the summary instead of preceding it.
Fixed
- Commit CI finds its project: a repository whose remote points at the connected GitLab or GitHub instance is associated automatically, so the toolbar indicator and its pipelines appear without opening the forge panel first. A project renamed on the forge is resolved through its redirect and its cached path refreshed; only remotes on the instance host are considered, so another forge's repository never borrows a same-named project.
Notes
- The update artifact is signed with the same key as 1.6.1: Settings → Updates offers 1.7.0, and “Return to the previous version” goes back to 1.6.1 through
rollback.json.