Re: Messed up trunk branch on gcc-test on forge

2025-08-20 Thread Jonathan Wakely via Gcc
On Wed, 20 Aug 2025 at 08:40, Claudio Bantaloukas wrote: > > I can set up the forge bot user to do a regular sync using the same infra > used for the PRs. > Just give the go ahead. That would be useful, thanks. gcc-TEST/master and gcc-TEST/trunk should both be sync'd with gcc-mirror/master on so

Re: Messed up trunk branch on gcc-test on forge

2025-08-20 Thread Claudio Bantaloukas via Gcc
I can set up the forge bot user to do a regular sync using the same infra used for the PRs. Just give the go ahead. From: Mark Wielaard Date: Wednesday, 20 August 2025 at 01:38 To: Andrew Pinski Cc: fo...@sourceware.org , gcc@gcc.gnu.org Subject: Re: Messed up trunk branch on gcc-test on

Re: Messed up trunk branch on gcc-test on forge

2025-08-19 Thread Mark Wielaard
Hi, On Tue, Aug 19, 2025 at 04:42:33PM -0700, Andrew Pinski wrote: > Hi all, > I accidentally messed up the trunk branch on gcc-test repo on the forge. > I clicked merge+fastforward button on a pull request thinking it was just a > rebase for the pull request. > Since it is just the test repo, I

Messed up trunk branch on gcc-test on forge

2025-08-19 Thread Andrew Pinski via Gcc
Hi all, I accidentally messed up the trunk branch on gcc-test repo on the forge. I clicked merge+fastforward button on a pull request thinking it was just a rebase for the pull request. Since it is just the test repo, I am not too worried at this stage. Is there a way to "revert" that pull reques