Filter out pull request related branches
Needs RevisionPublic
Actions

Authored by ardumont on Oct 4 2021, 4:18 PM.

Details

Reviewers

zack
douardda
olasd

Group Reviewers

Reviewers

Maniphest Tasks

T3627: Consider dropping pull request references from the git loader ingestion

Summary

Related to T3627

Test Plan

tox

Diff Detail

Repository

rDLDG Git loader

Branch

master

Lint

No Linters Available

Unit

No Unit Test Coverage

Build Status

Buildable 24194
Build 37770: Phabricator diff pipeline on jenkins	Jenkins console · Jenkins
Build 37769: arc lint + arc unit

Event Timeline

ardumont created this revision.Oct 4 2021, 4:18 PM

Build is green

Patch application report for D6401 (id=23277)

Rebasing onto 8d371e815c...

Current branch diff-target is up to date.

Changes applied before test

commit 111cd75d5367237c99d54766b140406069f2b484
Author: Antoine R. Dumont (@ardumont) <ardumont@softwareheritage.org>
Date:   Mon Oct 4 16:17:39 2021 +0200

    Filter out pull requests related branches
    
    Related to T3627

See https://jenkins.softwareheritage.org/job/DLDG/job/tests-on-diff/139/ for more details.

Harbormaster completed remote builds in B24194: Diff 23277.Oct 4 2021, 4:20 PM

ardumont requested review of this revision.Oct 4 2021, 4:20 PM

ardumont retitled this revision from Filter out pull requests related branches to Filter out pull request related branches.Oct 4 2021, 5:25 PM

ardumont mentioned this in T3627: Consider dropping pull request references from the git loader ingestion.Oct 6 2021, 2:38 PM

zack added a reviewer: zack.Oct 6 2021, 4:45 PM

LGTM

This revision is now accepted and ready to land.Oct 7 2021, 9:32 AM

This should stay pending until we resolve the archiving policy discussion in T3627, so I'm marking it as such.

This revision now requires changes to proceed.Oct 7 2021, 9:57 AM

This should stay pending until we resolve the archiving policy discussion in T3627, so I'm marking it as such.

Agreed, I'm adding myself as blocking reviewer, just in case.

Meanwhile, thanks all for the useful discussion in T3627. Let's see if we reach consensus there, otherwise this could be a good candidate for a swh-devel mailing list discussion too.