Page MenuHomePhabricator
Create Task
Maniphest T7470

show the base branch name in Differential revision info
Closed, DuplicatePublic
Actions

Description

In a differential patch, the web shows many fields of description including the author, reviewers, branch name, repo name,etc.

However, the base branch (landonto targeting branch) is not master at some case.

It would be great to see the 'landonto branch: xxx' field in such case.

Related Objects

Event Timeline

• lianghu created this task.Mar 6 2015, 2:43 AM
• lianghu assigned this task to epriestley.
• lianghu raised the priority of this task from to Normal.
• lianghu updated the task description. (Show Details)
• lianghu added a project: Differential.
• lianghu added a subscriber: • lianghu.

how about naming the fields as

base branch: xxx
feature branch: yyy

chad removed epriestley as the assignee of this task.Mar 6 2015, 2:49 AM
chad raised the priority of this task from Normal to Needs Triage.
• lianghu added a comment.Mar 6 2015, 3:06 AM

a side topic,

I saw "chad placed this task up for grabs".

What's grabs? I'm not aware of it.

chad added a subscriber: chad.Mar 6 2015, 3:19 AM

It means the task is unassigned.

• lianghu assigned this task to epriestley.Mar 10 2015, 2:43 AM

I think it should be assigned to Evan.

It's similar to D8359

chad removed epriestley as the assignee of this task.Mar 10 2015, 2:45 AM
chad added a subscriber: epriestley.
chad added a comment.Mar 10 2015, 2:52 AM

The is no need to assign a task, thanks!

• lianghu added a comment.Mar 10 2015, 2:55 AM

OK. Thanks for reminder.

Do you think this is a reasonable change request or not?

• lianghu added a comment.Mar 12 2015, 6:37 AM

When same code repo have different branches for different products.

It would be useful to identify a differential patch is for which branch.

chad added a comment.Mar 12 2015, 1:44 PM

T4778 covers how we prioritize tasks. Specifically we have thousands of requests, and are a very small team. We cannot provide any estimates when we'll even look to see if we should build this.

You may modify your local copy of Phabricator in the meantime to provide the functionality you need if the request is urgent.

jpoehls added a subscriber: jpoehls.Apr 15 2015, 1:44 PM
cburroughs added a subscriber: cburroughs.Jun 1 2015, 4:36 PM
epriestley moved this task from Backlog to Branch Handling on the Differential board.Dec 29 2016, 4:34 PM
Herald added a subscriber: eadler. · View Herald TranscriptDec 29 2016, 4:34 PM
epriestley added a comment.Apr 21 2017, 11:26 AM

I'm going to merge this into T10607.

We've showed this for some time:

Branch: feature (branched from master)

This is the brach that the feature branch was branched from.

However, the target branch (where the change will land) and the source branch (where the feature brach was branched from) are not necessarily the same. T10607 discusses that. If we made that change, we might show:

Branch: feature (branched from master, landing to development)

(This is rare.)

epriestley closed this task as a duplicate of T10607: Remote target/landing branch in Diff details.Apr 21 2017, 11:26 AM
epriestley added a comment.Apr 21 2017, 11:31 AM

Actually, that description is a little misleading, but I'll follow up in T10607.

Phabricator · Built by Phacility