On Mon, Jun 22, 2020 at 5:49 AM <[email protected]> wrote: > > This _was_ super handy because you need to be able to provide a list of > your ocmmits to google, but I guess the commits to your gitlab MR > suffice now; don't waste time on doing manual bookkeeping (or at least > as little as possible).
Gitlab is able to search the commit history for a given branch using the information known to it. See https://invent.kde.org/graphics/krita/-/commits/master?author=L.%20E.%20Segovia for instance Cheers, Ben > > On 2020-06-21 18:20, L. E. Segovia wrote: > > Hi Ben, > > > > We GSoC students (at least in the Krita project) have been requested > > to keep track of our progress via Phabricator tasks. Must we manually > > link to changes now? > > > > On 21/06/2020 03:38, Ben Cooksley wrote: > >> Hi all, > >> > >> With the completion of Phase 1 of our move to Gitlab, all code review > >> activity should now be taking place on Gitlab, with only residual > >> reviews being cleaned out of Phabricator (which hopefully we're > >> already well underway with - please start this if you haven't already) > >> > >> This leaves just Tasks left on Phabricator. > >> > >> As interacting with repositories isn't a core requirement for this > >> functionality, we've now taken the step of disabling all repository > >> functionality on Phabricator. > >> > >> This means that going forward, repositories will no longer be > >> browsable on Phabricator, nor will commit information be visible on > >> Phabricator. Additionally, actions normally taken via hooks (such as > >> "Differential Revision" and "Fixes Txxx") will no longer work. > >> > >> Should anyone have any questions regarding this, please let us know. > >> > >> Thanks, > >> Ben Cooksley > >> KDE Sysadmin > >> > > > > Best regards, > > > > amyspark >
