- Jan 16, 2020
-
-
Georges Racinet authored
-
Georges Racinet authored
From now on, we should upload this to PyPI, although it's still pretty useless without our *fork* of hg-git (that we can't have there).
-
- Jan 15, 2020
-
-
Georges Racinet authored
Because they are never called for other Git operations than receiving pushes, they are not expected to be triggered by local merges or imports.
-
Georges Racinet authored
-
Georges Racinet authored
I don't want to repeat all the flags here, it does not test anything behavioural.
-
- Jan 14, 2020
-
-
Georges Racinet authored
Rather than listing all these flags painfully on the command line of wherever imports are called from the Rails application, this simple setting will rule them all
-
Georges Racinet authored
A previous version had the required.hgrc at the top of the distribution, not in-package.
-
- Jan 10, 2020
-
-
Georges Racinet authored
-
Georges Racinet authored
Not merely installing install-requirements from the .gitlab-ci.yml because that would also install Mercurial, which is either a no-op or a costly ignored step.
-
- Jan 08, 2020
-
-
Georges Racinet authored
-
- Jan 07, 2020
-
-
Georges Racinet authored
-
Georges Racinet authored
- Jan 06, 2020
-
-
Georges Racinet authored
-
- Jan 05, 2020
-
-
Georges Racinet authored
We've always had the 'pushing to' message in Heptapod, but now that we're pushing directly on the FS without the entremise of SSH, it has become way too precise. At best it's a distraction, some would even consider it a disclosure of important information. At some point, we might in Heptapod use a completely new command instead of the generic push, but for the time being, we are reduced to this really hacky patching. This effectively silences everything except postclose hooks that `hg-git` will define – but it'll take care of them itself.
-
Georges Racinet authored
This can be used on top of the `required.hgrc` that we provide
-
Georges Racinet authored
Some of these could be enforced directly by the `heptapod` extension, but we want to make sure that they are still overridable by local admins.
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
pull-force-topic command See merge request !2
-
Georges Racinet authored
This is part of the refactoring of HGRC files that is motivated by running from source: it's cleaner to separate the user defined application-wide hgrc from the one bundled with Heptapod.
-
- Dec 25, 2019
-
-
Georges Racinet authored
-
- Dec 24, 2019
-
- Dec 21, 2019
-
-
Georges Racinet authored
This is part of heptapod#144: now that we're firing the pre-receive hook ourselves, we don't need to go over SSH at all. This also means that we don't need the `repositories-root` confiuration item anymore.
-
- Dec 19, 2019
-
-
Georges Racinet authored
This will be a major ingredient of SSH push support in Heptapod. Thanks to the factorizing effort we've done in `hooks.perm`, the implementation is almost trivial.
-
Georges Racinet authored
It's nicer and clearer to invoke it as `heptapod.hooks.perm.check_publish`
-
Georges Racinet authored
For now we just extract the generic part of `check_publish`.
-
- Dec 24, 2019
-
-
Georges Racinet authored
-
- Dec 18, 2019
-
-
Georges Racinet authored
As the docstring explains, this will help us somewhat with uniformity or how user information is passed around.
-
- Dec 19, 2019
-
-
Georges Racinet authored
-
- Dec 16, 2019
-
-
Georges Racinet authored
-
- Dec 15, 2019
-
-
Georges Racinet authored
updated the badges on README to reflect the default branch as well
-
Georges Racinet authored
-
Georges Racinet authored
and this uncovers a funny phenomenon, that hook gives an infinite loop when running on local Mercurial repos. Most of the work of the git_sync hook is done indirectly by the fact that `hg-git` rewraps the `push command`, but this still would catch stupid mistakes in that glue code, and `py-heptadod` is now 100% covered.
-
Georges Racinet authored
We don't need `repositories-root` if we have a fixed value for `mirror-path`. This allows us to shift indentation a bit, and that shouldn't be dangerous because the `mirror_path()` function is now fully tested
-
Georges Racinet authored
That one may sound futile, but it's actually a good thing to now that these debugging things are reliable, when using them to investigate actual problems.
-
Georges Racinet authored
We don't support Python3 at the time being, we'll jump into Python3-only at some time in the (near) future. With this, we have full coverage of the wsgi module. Hence the tests will catch true problems, thanks to Py3 incompatibility between `bytes` and `str`. This is better than adding a `pragma: no cover`.
-
Georges Racinet authored
since this wsgi server is meant for service the wire protocol of repos over HTTP only, the utility is a bit dubious, but let's honour it anyway. Normally, `hgweb_mod` should do it as well, but I couldn't get it to see a different config value (seems to be unsettable by .hg/hgrc)
-
Georges Racinet authored
that means actually testing that it's properly passed to `hgweb_mod`, the one doing the job
-