- 21 Nov, 2022 1 commit
-
-
Georges Racinet authored
-
- 17 Nov, 2022 1 commit
-
-
Georges Racinet authored
It happened at least once that even the wait on mergeability status was not enough.
-
- 10 Nov, 2022 1 commit
-
-
Georges Racinet authored
Useful for the catch-up merges we are currently doing. The goal is to allow to put `--create-mr` inconditionally instead of only after a few merge commits.
-
- 09 Nov, 2022 1 commit
-
-
Georges Racinet authored
We don't want to end up with topics that bring too much change from upstream. Non-merge changesets are a better metric than all changesets, as they represent the actual changes. The selected default, 200, seems to be a reasonable compromise for the current GitLab 15.x catch-ups.
-
- 10 Nov, 2022 2 commits
-
-
Georges Racinet authored
Unsurprisingly, it doesn't always work immediately to use `merge_when_pipeline_succeeds` immediately after the MR creation.
-
Georges Racinet authored
It was frustrating (and a calendar time waste) to get an error because of a forgotten argument or an expired token only at the end of the process.
-
- 23 Oct, 2022 1 commit
-
-
Georges Racinet authored
- don't stop the process if a Gitaly version change does not change the protocol - don't stop the process for patch-level GitLab Shell version changes
-
- 17 Oct, 2022 3 commits
-
-
Georges Racinet authored
This is the first use of GitLab API in this script. We use the same token default location as in `fetch-watch-tags` and probably will later on use the new `api` module from there as well.
-
Georges Racinet authored
Although not in use yet, it will need to be `store_true`
-
Georges Racinet authored
Makes help easier to understand
-
- 03 Oct, 2022 1 commit
-
-
Georges Racinet authored
Useful after stopping for inspection of Gitaly / GitLab Shell changes or even conflict resolution (if very simple or very early in the stack). Of course exclusive with `--heptapod-base-rev`
-
- 23 Sep, 2022 8 commits
-
-
Georges Racinet authored
This script repeatedly tries merges from the upstream GitLab trunk, starting from the current common ancestor of the `heptapod` branch. It stops at conflicts and when interesting conditions are met: - if the changeset under consideration or its children have tags, so that we will have changesets merging exactly the branching points of the stable branches - if Gitaly or GitLab Shell versions change: in that case, manual action is expected before submitting a MR The resulting merge is committed and pushed. Later on, we'll have also - conversion of the upstream Git repo (using `convert-pull-local` - Merge Requests and Issues creations
-
Georges Racinet authored
-
Georges Racinet authored
Could have led to nasty bugs when later on we'll switch to the EE repo (with EE content exclusing conversion of course)
-
Georges Racinet authored
This will be needed for operation on upstream EE repo.
-
Georges Racinet authored
We simply don't want the resulting bookmarks to be `15-0-stable-ee`, since we stripped actual EE content in the same way as GitLab bot does.
-
Georges Racinet authored
will be useful for non-stable branches (e.g, `master`, `main`)
-
Georges Racinet authored
This is important for virtualenv operation, especially when called from a surrounding script, such as `fetch-watch-tags` or the forthcoming auto-converter from upstream trunk.
-
Georges Racinet authored
It is useful while developing the script not to need the `default` path to be set.
-
- 08 Sep, 2022 9 commits
-
-
Georges Racinet authored
Better explained in the code comment.
-
Georges Racinet authored
Will make forthcoming change clearer
-
Georges Racinet authored
Part of heptapod#689
-
Georges Racinet authored
The point is to parse the version correctly. The Git repository will have either CE or EE stable branches, but not both. Part of heptapod#689
-
Georges Racinet authored
With heptapod#689, we will make the content match exactly what is in the CE edition repository. Therefore, we don't want the corresponding tags to be labelled `-ee`
-
Georges Racinet authored
As of hg-git 0.10.4, the hg-git tags file does not repeat any tag that also known as a global Mercurial tag. Our previous way of doing would therefore erase previously copied over tags. This in particular hg-git 1.0 suitable for the Heptapod upstream conversion.
-
Georges Racinet authored
On flake8 5.0.4, these non-necessary parentheses trigger "E275 missing whitespace after keyword"
-
Georges Racinet authored
This makes it testable, although we'll do it with the forthcoming changes only.
-
Georges Racinet authored
More convenient for development
-
- 01 Jul, 2022 1 commit
-
-
Georges Racinet authored
The checked out branch is always preceded by a star (and highlighted), hence it was missing. Problem is the branch we're most interested is the most likely to be checked out, especially right after a first release on a GitLab minor version. There's probably a nice plumbing command to call, maybe `git-for-each-ref`, but we need an immediate fix.
-
- 28 Mar, 2022 1 commit
-
-
Georges Racinet authored
-
- 05 Nov, 2021 1 commit
-
-
Raphaël Gomès authored
This ensures that we don't miss new releases.
-
- 21 Sep, 2021 1 commit
-
-
Georges Racinet authored
If it is used, the checkboxes for the corresponding tasks in the issue will be ticked according to the success of the conversion.
-
- 04 Oct, 2021 1 commit
-
-
Georges Racinet authored
We are about to launch subprocesses that will expect cwd to be this repository.
-
- 21 Sep, 2021 5 commits
-
-
Georges Racinet authored
will be useful for full automation
-
Georges Racinet authored
This is because we want to add more actions than just creating an issue for each version, and the resulting issue will depend on these actions.
-
Georges Racinet authored
Will make further refactorings easier
-
Georges Racinet authored
This means in particular that `filter_new_versions` has to be adapted to work on `GitLabVersion` instances.
-
Georges Racinet authored
In the forthcoming improvements, we will have more callers for the stable branch name etc.
-
- 10 Jul, 2021 2 commits
-
-
Georges Racinet authored
I've almost always been adding those line continuations manually since I started using those instructions. This is probably one of the last changes before launching the two migrations automatically.
-
Georges Racinet authored
-