This instance will be upgraded to Heptapod 0.26.0rc1 on 2021-10-26 at 14:00 UTC+2 (a few minutes of down time)

Commit dd3ddc29 authored by Pierre-Yves David's avatar Pierre-Yves David 🐙
Browse files

readme: update contribution guide

We move to heptapod !

--HG--
branch : stable
parent d1066fb2c95a
Pipeline #958 passed with stage
in 15 minutes and 5 seconds
......@@ -116,16 +116,17 @@ Bugs are to be reported on the mercurial's bug tracker (component: `evolution`_)
.. _evolution: https://bz.mercurial-scm.org/buglist.cgi?component=evolution&query_format=advanced&resolution=---
You can use the patchbomb extension to send email to `mercurial devel
<https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel>`_. Please make
sure to use the evolve-ext flag when doing so. You can use a command like
this::
The recommended way is to create Merge Request on
https://dev.heptapod.net/mercurial/evolve. To do so, create an account and
request access. You'll then be able to create topic based merge request.
$ hg email --to mercurial-devel@mercurial-scm.org --flag evolve-ext --rev '<your patches>'
Alternatively, you can use the patchbomb extension to send email to `mercurial
devel <https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel>`_.
Please make sure to use the evolve-ext flag when doing so. You can use a
command like this::
Some of development happens on a public bitbucket repository (`evolve-devel`_) using the topic extension.
$ hg email --to mercurial-devel@mercurial-scm.org --flag evolve-ext --rev '<your patches>'
.. _`evolve-devel`: https://bitbucket.org/octobus/evolve-devel
For guidelines on the patch description, see the `official Mercurial guideline`_.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment