P.S.: please "Reply All" to this email as I am not subscribed to this
list
What tool, if any, is gioui using to mirror the sr.ht repo to GitHub? I
have a repo where I would like to do this
- https://git.sr.ht/~eliasnaur/gio
- https://github.com/gioui/gio
I apologize if this question's been answered before and I couldn't find
it in the list's archive.
--
David
If you have both remotes attached to your version you can push up both remotes. When I do PRs on github I often have the original plus my fork with the branch so I can grab upstream updates, I usually call the upstream "upstream" but of course I don't have push access on the main/master. But if you did, you could easily do this and synchronise them both this way.
Sincerely,
David
Sent with Proton Mail secure email.
------- Original Message -------
On Sunday, August 28th, 2022 at 01:47, David Florness <david@florness.com> wrote:
> P.S.: please "Reply All" to this email as I am not subscribed to this> list> > What tool, if any, is gioui using to mirror the sr.ht repo to GitHub? I> have a repo where I would like to do this> > - https://git.sr.ht/~eliasnaur/gio> - https://github.com/gioui/gio> > I apologize if this question's been answered before and I couldn't find> it in the list's archive.> > --> David
Thanks for the reply, David!
David Vennik <david@cybriq.systems> writes:
> If you have both remotes attached to your version you can push up both> remotes. When I do PRs on github I often have the original plus my fork with the> branch so I can grab upstream updates, I usually call the upstream "upstream"> but of course I don't have push access on the main/master. But if you did, you> could easily do this and synchronise them both this way.
That makes sense; it just seems like it would be slightly annoying to
keep all branches constantly in sync between 2 or more remotes, so a
light wrapper script that handles that automatically would make life a
bit easier.
I now realize, however, that in gio's case, only the main branch is
being synchronized (no other branches nor tags nor tickets/issues), so
the problem doesn't really exist here.
Thanks again,
--
David
> I now realize, however, that in gio's case, only the main branch is> being synchronized (no other branches nor tags nor tickets/issues), so> the problem doesn't really exist here.
This is how we mirror:
https://git.sr.ht/~eliasnaur/gio/tree/main/item/.builds/linux.yml#L56
We just don't have issue tracking on github, so you have to use our
sourcehut one. The other option is:
https://github.com/aThorp96/sourcehut_issue_mirror
A github action to redirect issues to sourcehut trackers.
Our CI approach can be extended to push all branches/tags. However,
you have to pick one repo as the source of truth and only make write
changes to the repo there. Otherwise you can create some real
headaches.
Cheers,
Chris