This instance will be upgraded to Heptapod 0.21.0rc2 on 2021-04-16 at 14:00 UTC+2 (a few minutes of down time)

CONTRIBUTING 1.35 KB
Newer Older
1 2
The short version:
 * Patches should have a good summary line for first line of commit message
3 4
 * Patch series should be sent primarily as Merge Requests[1] or to the
   Google Group[0]
5
 * Patch needs to do exactly one thing
6
 * test suite passes (enforced by continuous integration)
7 8 9 10

The longer version:

We use a variant of Mercurial's own contribution
11
system. https://www.mercurial-scm.org/wiki/ContributingChanges contains
12 13
their full guidelines. Key differences are (by rule number):

14 15 16 17
 1. For hg-git, we're not strict about the "topic: a few words" format
    for the first line, but do insist on a sensible summary as the
    first commit line
 2. You can cross-reference Heptapod issues in the #NNN format
18 19 20
 10. We use mostly pep8 style. The current codebase is a mess, but new
     code should be basically pep8.

21 22 23 24
0:
Mailing list: hg-git@googlegroups.com
Archives: https://groups.google.com/forum/#!forum/hg-git

25 26 27 28 29 30 31 32 33 34 35
1:
The project is hosted at https://foss.heptapod.net/mercurial/hg-git

To submit a Merge Request, please ask for Developer rights using the
'Request access' link. Then, following the instructions of the following
tutorial should be enough:
https://heptapod.net/pages/quick-start-guide.html

If you do a Merge Request, we're still going to expect you to
provide a clean history, and to be willing to rework history so it's
clean before we push the "merge" button.