Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot create named bookmark #158

Open
dwmw2 opened this issue Mar 19, 2018 · 1 comment
Open

Cannot create named bookmark #158

dwmw2 opened this issue Mar 19, 2018 · 1 comment
Labels
ux User experience

Comments

@dwmw2
Copy link

dwmw2 commented Mar 19, 2018

I'm trying to use this to work with Pidgin, having forked the repository on bitbucket.org.

In order to have more than one pull request open at a time without having to fork a completely new repository for each, I need multiple heads in the release-2.x.y branch.

I can do this... commit one set of patches and push thus:

$ git push testfork HEAD:branches/release-2.x.y/search
Bundling 2 changesets
Bundling 2 manifests
Bundling 2 files
remote: adding changesets
remote: adding manifests
remote: adding file changes
remote: added 2 changesets with 2 changes to 1 files (+1 heads)
remote: 
remote: Create pull request for release-2.x.y:
remote:   https://bitbucket.org/dwmw2/testfork/pull-requests/new?source=release-2.x.y&t=1
remote: 
To hg::ssh://[email protected]/dwmw2/testfork
 * [new branch]      HEAD -> branches/release-2.x.y/search

But the names of the bookmarks are dropped, and I just get a bare commit-id next time I fetch:

$  git fetch testfork
From hg::ssh://[email protected]/dwmw2/testfork
 x [deleted]         (none)     -> testfork/branches/release-2.x.y/search
 x [deleted]         (none)     -> testfork/branches/release-2.x.y/transient
Reading 5 changesets
Reading 5 manifests
Reading and importing 7 files
Importing 5 manifests
Importing 5 changesets
 * [new branch]      branches/release-2.x.y/57c79c1ff470bb5cd67d8ff6edb8af5d81cf4074 -> testfork/branches/release-2.x.y/57c79c1ff470bb5cd67d8ff6edb8af5d81cf4074
 * [new branch]      branches/release-2.x.y/959f11ec42921042a4c70f07e9069c590461bcde -> testfork/branches/release-2.x.y/959f11ec42921042a4c70f07e9069c590461bcde
 + 03c144f...1270e95 branches/release-2.x.y/tip -> testfork/branches/release-2.x.y/tip  (forced update)

AFAICT, submitting a pull request from an unnamed head means that I can't subsequently update it if changes are requested.

@glandium
Copy link
Owner

Sorry for this late response. I left this on a side of my mind as some sort of missing feature, but revisiting this report, I'm now wondering if it's not only a documentation or UX issue. I think what you want is to push to bookmarks/search and bookmarks/transient instead of branches/release-2.x.y/search and branches/release-2.x.y/transient. AFAIK, mercurial bookmarks are not specifically attached to mercurial branches.

@glandium glandium added the ux User experience label Jul 14, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ux User experience
Projects
None yet
Development

No branches or pull requests

2 participants