mirror of
https://we.phorge.it/source/arcanist.git
synced 2024-11-26 00:32:41 +01:00
make arcanist backwards compatible with various conduit versions
Summary: pragmatism wins the day, though I think eventually we might want something really fancy to deal with arcanist and conduit not being up to date with respect to one another Test Plan: php -l Reviewers: epriestley Reviewed By: epriestley CC: zeeg, aran, Korvin Maniphest Tasks: T2088 Differential Revision: https://secure.phabricator.com/D3988
This commit is contained in:
parent
5ca0f691a1
commit
b71666a24a
1 changed files with 6 additions and 4 deletions
|
@ -940,10 +940,12 @@ abstract class ArcanistBaseWorkflow {
|
|||
}
|
||||
$bundle = ArcanistBundle::newFromChanges($changes);
|
||||
$bundle->setConduit($conduit);
|
||||
$bundle->setProjectID($diff['projectName']);
|
||||
$bundle->setBaseRevision($diff['sourceControlBaseRevision']);
|
||||
$bundle->setRevisionID($diff['revisionID']);
|
||||
$bundle->setAuthor($diff['author']);
|
||||
// since the conduit method has changes, assume that these fields
|
||||
// could be unset
|
||||
$bundle->setProjectID(idx($diff, 'projectName'));
|
||||
$bundle->setBaseRevision(idx($diff, 'sourceControlBaseRevision'));
|
||||
$bundle->setRevisionID(idx($diff, 'revisionID'));
|
||||
$bundle->setAuthor(idx($diff, 'author'));
|
||||
return $bundle;
|
||||
}
|
||||
|
||||
|
|
Loading…
Reference in a new issue