- Feb 23, 2020
-
-
Georges Racinet authored
-
- Feb 19, 2020
-
-
Georges Racinet authored
-
- Feb 15, 2020
-
-
Georges Racinet authored
These will be exposed first through the REST API (this is heptapod#165), then we'll probably want them to be displayed and writeable from the Web UI. Compared to the lower level versions, they have several advantages: - clearer namings: the lower level knobs have names that are make sense independently of the context, but in Heptapod, we can make more assumptions about the context, and hence come up with something more immmediately meaningful to users - easier to remember, less frightening (it's not more experimental than Heptapod itself) - several flags can be set at once (see the case of bookmarks) For now, the rule is that they are really inert if not set, so that we don't interfere with tweakings of the lower level settings our users may already have performed. It's also the occasion to introduce `auto-publish=all`, which makes a project entirely publishing - can be the preferred way for some.
-
Georges Racinet authored
This tests the patch of `ui._runsystem` that forwards environment variables to external hooks
-
Georges Racinet authored
reducing duplication is always good. In this case it makes the config of each test clearer.
-
Georges Racinet authored
One less thing to tweak when we switch to Python 3
-
- Feb 05, 2020
-
-
Georges Racinet authored
-
Georges Racinet authored
-
- Jan 30, 2020
-
-
Georges Racinet authored
This is needed in particular so that they are in Heptapod backups
-
Georges Racinet authored
-
Georges Racinet authored
Currently that's also 5.3rc1, should diverge to be a 5.4 dev version soon.
-
Georges Racinet authored
hg-evolve 9.2.1 is simply not compatible with hg 5.3rc1 anymore
-
- Jan 23, 2020
-
-
Georges Racinet authored
-
Georges Racinet authored
-
- Jan 21, 2020
-
-
Georges Racinet authored
This is necessary for heptapod#169: the caller needs a clear indication that the pull was empty. The choice of return code is consistent with `push` exiting also in code 1 if there is no changeset to push (but still pushing phase changes)
-
- Jan 19, 2020
-
-
Georges Racinet authored
This is necessary for heptapod#169: the caller needs a clear indication that the pull was empty. The choice of return code is consistent with `push` exiting also in code 1 if there is no changeset to push (but still pushing phase changes)
-
- Jan 17, 2020
-
-
Georges Racinet authored
clearly a leftover of past hesitations about the variable
-
- Jan 16, 2020
-
-
Georges Racinet authored
What this really does is make `ui.system()` pass the `HEPTAPOD_*` environment variables to the resulting subprocess. Since `ui.environ` is used as a WSGI request-local substitute to the (process-wide) environ, the question whether it should be always fully forwarded will have to be raised in Mercurial upstream. In the meanwhile, Heptapod will pass its variables to external hooks. Closes: heptapod#72
-
- Jan 19, 2020
-
-
Georges Racinet authored
-
- 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
-