Trouble with first commit
i'm having trouble following the steps for my first simple commit (looking at contributing.html). I applied for and was granted access yesterday. I've connected my github account. When i try to do the push i get 'remote: user "heptapod-write" is not authorised to publish changesets' Any help would be much appreciated! ...the steps I followed mkdir local_src cd local_src hg clone https://foss.heptapod.net/pypy/pypy cd pypy # edit pypy/.hg/hgrc # add # username = shaolo1 <shao.lo@gmail.com> hg pull && hg up hg branch build_link_fix # ...edit file build.rst hg commit -m "Replaced bad link to getting-started-dev.html with contributing.html." hg push pushing to https://foss.heptapod.net/pypy/pypy searching for changes abort: push creates new remote branches: build_link_fix! (use 'hg push --new-branch' to create new remote branches) hg push --new-branch pushing to https://foss.heptapod.net/pypy/pypy searching for changes http authorization required for https://foss.heptapod.net/pypy/pypy realm: GitLab user: shaolo1 password: remote: adding changesets remote: adding manifests remote: adding file changes remote: user "heptapod-write" is not authorised to publish changesets: a2ceee6a2d79 abort: push failed on remote
Our documentation is not as clear on this aspect as it could be. After having been granted access, by default you can only make "short-lived" branches (with `hg topic foo`) but not "long-lived" branches (`hg branch foo`). It seems like in your case, it’s just a matter of replacing `hg branch build_link_fix` with `hg topic build_link_fix`. You can also change it after the fact: * (Your changeset has hash a2ceee6a2d79.) * First, you can reset the branch: `hg branch default -r a2ceee6a2d79`. Now, your changeset has a new hash. * Then, you can set the topic `hg topic build_link_fix -r <new hash>`. If you already have multiple changesets, you can pass `-r` multiple times or pass a revset. On 2020-06-09 21:13, shao lo wrote:
Our documentation is not as clear on this aspect as it could be. After having been granted access, by default you can only make "short-lived" branches (with `hg topic foo`) but not "long-lived" branches (`hg branch foo`). It seems like in your case, it’s just a matter of replacing `hg branch build_link_fix` with `hg topic build_link_fix`. You can also change it after the fact: * (Your changeset has hash a2ceee6a2d79.) * First, you can reset the branch: `hg branch default -r a2ceee6a2d79`. Now, your changeset has a new hash. * Then, you can set the topic `hg topic build_link_fix -r <new hash>`. If you already have multiple changesets, you can pass `-r` multiple times or pass a revset. On 2020-06-09 21:13, shao lo wrote:
participants (2)
-
Manuel Jacob -
shao lo