Does the gcc/gcc-TEST fork sync from gcc/gcc-mirror?

Guinevere Larsen guinevere@redhat.com
Wed Oct 23 12:01:02 GMT 2024


On 10/23/24 8:56 AM, Jonathan Wakely wrote:
>
> How often does the forge mirror sync from the official git repo? And 
> does the gcc/gcc-TEST fork ever sync, or does that have to be manually 
> updated by tschwinge or another owner?
>
> I want to create a PR with a single commit, but because my local tree 
> is up to date with the official repo, but gcc/gcc-TEST isn't, my PR 
> includes two commits by other people. That's not ideal.
>
> e.g. 
> https://forge.sourceware.org/gcc/gcc-TEST/compare/master...redi/gcc:test-docs-example
>
> At the time of writing, this PR will try to merge three commits into 
> the gcc-TEST fork. But only the libstdc++ one is what I want to 
> include in the PR. The others are upstream in gcc.gnu.org/git/gcc.git 
> <http://gcc.gnu.org/git/gcc.git> but not in the gcc-TEST fork yet.
>
> Do I need to maintain a separate local branch that is sync'd with 
> gcc-TEST instead of the official repo, and create pull reqs based on that?
>
I was about to email about this. My limited experience with github says 
if you want to keep your fork up-to-date, it needs a pull-request from 
the original repo to your fork. Manual updating.

However, this also doesn't seem to work on forgejo, because you can't 
create PRs from mirrors either. My best guess would be to pull locally 
from the mirror, then push to the fork, locally on your computer.

Maybe Mark knows a way to do it automatically with forgejo, though...

-- 
Cheers,
Guinevere Larsen
She/Her/Hers
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://sourceware.org/pipermail/forge/attachments/20241023/188f1cd7/attachment.htm>


More information about the Forge mailing list