Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

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

unisonweb / unison Public

Notifications You must be signed in to change notification settings
Fork 273
Star 5.9k

Code
Issues 1.1k
Pull requests 47
Discussions
Actions
Projects
Wiki
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Wiki
Security
Insights

Track and use last known remote hash in pullv2#5571

Draft

ChrisPenner wants to merge 3 commits intotrunkunisonweb/unison:trunkfrom syncv2/track-remote-headunisonweb/unison:syncv2/track-remote-headCopy head branch name to clipboard

+72-17

Conversation Commits3 (3)Checks Files changed

Commits

Commits on Feb 13, 2025

Track latest known remote for cloned/pushed projects
ChrisPenner
committed
Use last-known remote branch instead of causal negotiation
ChrisPenner
committed
Add remote head hash in new codebases
ChrisPenner
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.