It would be very useful if Favro's GitHub Source Control integration could display development information directly on the related Favro card, similar to Jira's Development panel.

At the moment, the Source Control integration is primarily focused on receiving GitHub events and creating automation rules, such as moving cards based on commits or pull requests. However, there is no clear development overview visible on the card itself.

Proposed functionality

When a GitHub branch, commit, or pull request references a Favro card ID such as BOK-7103, Favro could automatically show a Development / Source Control section on that card containing information such as:

Linked branch name

Branch status

Pull request number and title

Pull request status: Draft / Open / Merged / Closed

Review status: Pending / Approved / Changes requested

Number of commits

Latest commit

Merge status / conflicts

CI/check status, if available

Direct links to the branch, commits, and pull request

For example:

Development

Branch: BOK-7103

Pull Request: #2010 – BOK-7103 Fix variable names

Status: Open

Review: Changes requested

Merge status: No conflicts

Commits: 2

Use case

Our developers already use the Favro card ID in branch names, commit messages, and pull requests.

For example:

Branch: BOK-7103

Commit: BOK-7103 - fix: variable names and related code

This makes it possible for Favro to associate GitHub activity with the correct card.

However, project managers, QA, designers, and other team members currently have to open GitHub separately to understand the development status of the task.

Having this information directly on the Favro card would make the card the central place for tracking the complete lifecycle of a task.

Why this would be valuable

It would allow the whole team to quickly answer questions such as:

Has development started?

Is there already a branch?

Is a pull request open?

Is the PR waiting for review?

Have changes been requested?

Has the PR been approved?

Is it ready to merge?

Has it already been merged?

This would make Favro's GitHub integration significantly more useful for software-development teams and provide functionality comparable to Jira's GitHub/Development integration.

Suggested behavior

The existing GitHub Source Control integration could remain responsible for automation rules, while the card additionally gets a read-only Development section showing the current GitHub state.

Ideally, Favro would automatically associate development activity whenever the Favro card ID is present in:

Branch name

Commit message

Pull request title

Pull request description

This would provide both workflow automation and development visibility without requiring users to leave Favro.