Branching and Turning on Flow Control
I believe I have read somewhere that HgLabs does not currently support Branches?
If so, then what is the suggested work around?
Can I branch a local repo and then push it back up to HgLab server where it will then show up in the Branches?
Can I install TortoiseHg onto my HgLabs 1.75 server?
And then use a cmd line Hg or a TortoiseHg gui to branch something on the server?
obviously i'll try this pretty soon but after getting the server running, I hate to mess with it.
Finally, I see other discussions about Flow Control vs. Branching but I don't see where I would activate that on my repos/
Thanks
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by pdavidson on 13 Nov, 2014 12:39 AM
I see from your blog that Flow is turned on automatically if you have installed the python module for it. I believe that answers the question of Flow
Support Staff 2 Posted by Anton Gogolev on 13 Nov, 2014 08:42 AM
Paul,
Depends on what you mean by "support Branches". What HgLab does not support is Forks and Merge Requests. It knows very well about named branches: e.g. http://live.hglabhq.com/projects/hgsharp/repositories/hgsharp/branches. All branches you create locally and then push up to HgLab will be displayed on this page.
On the server side, HgLab supports Flow without installing anything extra. The "Flow" tab is activated automatically as soon as HgLab sees the
.flowor.hgflowfile present.On the client side, a Mercurial extension is required.
You can indeed install TortoiseHg on the server, but there's no point in having it there.
3 Posted by pdavidson on 14 Nov, 2014 02:31 AM
Tx, makes sense now. Named branches working just fine.
Anton Gogolev closed this discussion on 14 Nov, 2014 04:37 PM.