Phabricator¶
You can import tasks from your Phabricator instance using
the phabricator
service name.
Example Service¶
Here’s an example of an Phabricator target:
[my_issue_tracker]
service = phabricator
Note
Although this may not look like enough information for us
to gather information from Phabricator,
but credentials will be gathered from the user’s ~/.arcrc
.
The above example is the minimum required to import issues from Phabricator. You can also feel free to use any of the configuration options described in Common Service Configuration Options.
Service Features¶
If you have dozens of users and projects, you might want to pull the tasks and code review requests only for the specific ones.
If you want to show only the tasks related to a specific user, you just need to add its PHID to the service configuration like this:
phabricator.user_phids = PHID-USER-ab12c3defghi45jkl678
If you want to show only the tasks and diffs related to a specific project or a repository, just add their PHIDs to the service configuration:
phabricator.project_phids = PHID-PROJ-ab12c3defghi45jkl678,PHID-REPO-ab12c3defghi45jkl678
Both phabricator.user_phids
and phabricator.project_phids
accept
a comma-separated (no spaces) list of PHIDs.
If you specify both, you will get tasks and diffs that match one or the other.
If you do not know PHID of a user, project or repository,
you can find it out by querying Phabricator Conduit
(https://YOUR_PHABRICATOR_HOST/conduit/
) –
the methods which return the needed info are user.query
, project.query
and repository.query
respectively.
Provided UDA Fields¶
Field Name | Description | Type |
---|---|---|
phabricatorid |
Object | Text (string) |
phabricatortitle |
Title | Text (string) |
phabricatortype |
Type | Text (string) |
phabricatorurl |
URL | Text (string) |