- Jul 05, 2021
-
-
Georges Racinet authored
of course, with a different initial version.
-
Georges Racinet authored
The only immediate application is to test PEP440 compliance, but the motivation was rather that it's now very easily done.
-
Georges Racinet authored
Granted, it's been completely trivial so far, will be a bit less in a minute.
-
Georges Racinet authored
This is the same as what's been done a while ago in hgitaly@27f3a6ac3278. Benefits: - uniformity in release procedure with HGitaly - easier to script (actually also easier to hand edit)
-
- Jul 01, 2021
-
-
Georges Racinet authored
That is why it's not so good an idea to make a topic for release matters (forgot to update after pull). In that precise case, it's not worth a new version
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
Because the post-receive hook is now called in the locks release callback, we need to make sure it doesn't use anything that the release just invalidated, notably weak refs. But the hooks were only using the repository object for - the path to the repository (taking sharing into account) - `repo.ui` We now extract these two elements, and immediately delete the reference to the repository object. Both linters and the tests with full coverage complete the proof that no other use is occurring.
-
Georges Racinet authored
This is a merge of change done on the stable branch, where it was restricted to Merge Request creations by pushvars to limit the risks. In all cases, it makes sense to send the post-receive only after new writes are permitted, because there's no telling what writes the Rails app would need to perform directly. As far as I understand, Git locking is weaker than Mercurial's, as it happens on a file-per-file basis. That's why the Rails app could easily grow new problematic writes that wouldn't be rejected by locks in the Git case.
-
Georges Racinet authored
…and it will match Heptapod 0.23, while Heptapod 0.22 has 2.7
-
- Jun 25, 2021
-
-
Georges Racinet authored
Because the Rails application can perform Mercurial writes synchronously during treatment of the post-receive API call, we need the latter to happen only after full locks release. The only currently know case happens during Merge Request, creation, hence we change the behaviour on this stable branch only in that case. It would probably be better to make this inconditionally for the default branch (after all PostReceive should mean the reception is fully done). Closes heptapod#505
-
- Jun 24, 2021
-
-
Sushil Khanchi authored
Adding newly added cmd `hpd-ensure-gitlab-default-branch` to `hpd-ensure-all-gitlab-specific-state-files` as later one is responsible for existence of all state files specific to gitlab.
-
Sushil Khanchi authored
New alias `hpd-ensure-all-gitlab-specific-state-files` which will make more sense after we add a new command call in next patch. `hpd-ensure-all-gitlab-refs` name will be removed once we start calling new name at Rails side.
-
- Jun 23, 2021
-
-
Sushil Khanchi authored
-
- Jun 16, 2021
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
In many articulation places, we make sure not to transmit an empty dict, in order not to update all existing tests. Because pushvars have to be a a mapping (as environment variables in the CLI, already parsed as a dict in the internal API) and Git options are arbitrary strings (which GitLab can interpret as mapping if they have the `=` token), we decided arbitrarily to translate as follows: value is empty string -> send just the key otherwise, send `key=value` Later on we can have the CLI parser of Mercurial also accept just `KEY` to be synonymous of `KEY=`.
-
- Jun 11, 2021
-
-
Georges Racinet authored
-
Georges Racinet authored
Part of heptapod#496
-
- May 27, 2021
-
-
Georges Racinet authored
-
Georges Racinet authored
-
- May 26, 2021
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
Closes heptapod#482
-
- May 25, 2021
-
-
Georges Racinet authored
-
Georges Racinet authored
-
Georges Racinet authored
Apparently, it is possible for the ImportError to be raised immediately, and not at first attribute access, making thus the latter uncovered
-
- May 22, 2021
-
-
Georges Racinet authored
The move to `hgext3rd.hggit` is about to happen and will be released first with version 0.11.0
-
- May 20, 2021
-
-
Georges Racinet authored
-
Georges Racinet authored
-
- May 14, 2021
-
-
Georges Racinet authored
-