Welcome. You should be able to push a branch to the repo. So the workflow is similar-but-not-quite-exactly-like github:
hg clone https://foss.heptapod.net/pypy/cffihg up defaulthg branch tutorial-packaging<modify some rst pages><run cd doc; make html to view the docs>hg commit -m"<my message>"hg log # view the commit, make sure it is what you wanthg push
Ehm... I logged here using my github account.
Now I have a first draft to push, but hg asks for a password and it will not accept my github pass.
What should I do?
mcon@cinderella:~/PDF/cffi/doc$ hg push --new-branchpushing to https://foss.heptapod.net/pypy/cffisearching for changeshttp authorization required for https://foss.heptapod.net/pypy/cffirealm: GitLabuser: mcondarellipassword: remote: adding changesets remote: adding manifestsremote: adding file changesremote: You are not authorised to publish changesets: 63b0c59b0049For more information about topics auto-publishing rules in Heptapod, see: https://heptapod.net/pages/faq.html#bare-draftabort: push failed on remote
According to the permissions table, developers should be able to push to unprotected branches. Maybe because there are no unprotected protected branches the default is to disallow pushes to any branch?
Yes, in basic GitLab (in Heptapod context, read: on Git projects),
Developers can push to any unprotected branch.
But in the Mercurial case comes another limitation: only Maintainers
have the right to publish (or push public) changesets. With the default
auto-publication of changesets without topics, that amounts to saying
that only Maintainers can push non-topic changesets.
This, together with how to change the settings with the REST API, is
documented here. Like
any piece of documentation, it can certainly be improved, of course.
Yes, I like the "tried this, it failed, here's why" story flow. I sometimes see people using python to parse the header files and cut out the parts that pycparser cannot deal with, rather than cut-and-pasting the needed structures to a new header file, but this is your story not mine :).