1 |
On 6/4/20 2:36 AM, Robert Günzler wrote: |
2 |
> Did you take a look at https://sourcehut.org at all? I think the |
3 |
> direction they're going with fusing the email and web-based workflows is |
4 |
> nice: https://sourcehut.org/blog/2019-10-15-whats-cooking-october-2019/ |
5 |
> |
6 |
> robert |
7 |
> |
8 |
Maybe the paste service comes closest to what I'd be looking for here. |
9 |
Basically a simple wgettable git-format patch-file. |
10 |
|
11 |
My workflow example: |
12 |
|
13 |
1: Open https://github.com/gentoo/gentoo/pull/16029 |
14 |
|
15 |
2: Launch a container with up-to-date ~ stage3, |
16 |
|
17 |
3: "fullget.sh 16029" (a bash script to download |
18 |
https://patch-diff.githubusercontent.com/raw/gentoo/gentoo/pull/XXXXXX.patch |
19 |
and apply it to containers portage tree)(fullget.sh, because there is |
20 |
another script to cherry-pick commits), |
21 |
|
22 |
4: pkgcheck scan --commits, |
23 |
|
24 |
5: depmerge.sh package (emerge -1av --onlydeps --with-test-deps "$@"), |
25 |
|
26 |
6: testmerge.sh package (emerge -1av with |
27 |
https://wiki.gentoo.org/wiki/Package_testing#make.conf these settings), |
28 |
|
29 |
7: If all is good, switch to desktop shell and ::gentoo repo, use "pram |
30 |
16029" (https://packages.gentoo.org/packages/app-portage/pram) |
31 |
|
32 |
(I'm looking to automate steps 3-6 with one command) |
33 |
|
34 |
|
35 |
With e-mail patches, I have to copypaste them manually into container, |
36 |
and then apply them manually to ::gentoo repo one-by-one. It's not a lot |
37 |
extra work, but it slows down the process a bit. And reviewing |
38 |
contribution is a bit tedious compared to Github, especially if there is |
39 |
a big contribution. |
40 |
|
41 |
-- juippis |