You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For a GIT repository in the Activities view there is no indication on the branch upoun witch the commit was pushed.
Moreover this information is not present nor in the "Details" of a commit nor in the "Sources".
Proposed solution
Add the name of the branch as a link in all those views allowing to navigate to the repository code sources specific branch.
As a sidenote, I would suggest to consider ordering the branches in the select box of the repository code view based on the time of the last commit on each branch, putting the last actives on top.
It could be usefull to quickly discover the most active branches.
The text was updated successfully, but these errors were encountered:
Yes after I've written the suggestion I discover that in brach overview there is already a sorting of the branches based on activity.
I think that's very good.
And probably more than enought, instead of sorting the dropdown.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
stalebot
added
the
stale
Issue is stale and will be closed if no further activity occurs
label
Aug 7, 2021
Feature Request
Problem to be solved
For a GIT repository in the Activities view there is no indication on the branch upoun witch the commit was pushed.
Moreover this information is not present nor in the "Details" of a commit nor in the "Sources".
Proposed solution
Add the name of the branch as a link in all those views allowing to navigate to the repository code sources specific branch.
As a sidenote, I would suggest to consider ordering the branches in the select box of the repository code view based on the time of the last commit on each branch, putting the last actives on top.
It could be usefull to quickly discover the most active branches.
The text was updated successfully, but these errors were encountered: