[enhancements] Foundry Branching provenance/visibility

Product Feedback
,
1

Foundry branching is great and we’re loving the new features/support, but I think we could improve visibility for merged branches in a few ways:

  1. First, when looking at a merged branch in the Foundry Branching activity, there is no information about the data that was included in that branch – only a link to the merged proposal. In the proposal, only the resources that were changed are listed here (and are hyperlinked only to the master branch version of the resource, with no link to the associated PR (speaking at least for Authoring changes). enhancements: (a) Show the merged changes with the same interactive diff view we get when reviewing a new proposal. (b) include a hyperlink to the associated proposal/PR for any pipeline changes
  2. In Code Repositories (using an example of a change created by AI FDE), we rely on line blame and the File Changes view in the bottom panel. Line blame shows the changes were authored by Foundry (authoring) rather than the requesting engineer, and the File Changes card list view shows something like Deployment of branch ri.branch..branch.... and deployment abcdef.... with no mention of the initiating user or a link to the merged pull request (which was the default behavior for local foundry branch/PRs). enhancements: (a) (Less important - but would be nice) - change line blame to reflect the initiating user as AI FDE is used as an extension of the current user, not autonomously, (b) include a hyperlink to the merged pull request in the commit comment, (c) include the branch name in the commit comment, (d) add the initiating user’s name in the commit comment; (both (b), (c), & (d) will then provide more context in both the Commit view and in the File Changes view.
  3. Neither Code Repository Pull Requests nor Pipeline Builder Proposals that are created automatically from Foundry Branching include a link back to the Proposal (though the proposal RID is included). enhancement. For branches created via AI FDE, the initiating user is not evident (a) include a URL to the foundry proposal, (b) include the initiating user in the PR/Proposal comments
4 Likes
2

One more (easy) minor enhancement - within Code Repositories the View pull request button is dithered when the pull request is associated with a proposal in foundry branching - could we restore this link so we don’t need to access that PR via multiple clicks ((a)click View Proposal in the foundry branch footer, (b) Click View by the listed repository)

1 Like