Is your feature request related to a problem? Please describe.
If people make the slightest changes to their builds, the commit ID will not show where they are in terms of syncing with Trio upstream. If we add parent commit refs to the build details displayed at the top of Settings view, we will probably be able to se recent merges with Trio main/dev/alpha as parent commits.
Describe the solution you'd like
Make minor adjustments to the current code for getting and displaying build details
Describe alternatives you've considered
List and describe any alternative solutions or features you've considered that could also address the problem. Explain why you believe the proposed solution is the best option.
Additional context
Include any other context, screenshots, or relevant information that might help in understanding the issue or the proposed solution. If applicable, describe any previous discussions or decisions that relate to this feature request.
Technical Details
If applicable, provide any technical details or considerations that might impact the implementation of this feature. This could include dependencies, potential risks, or required changes to existing functionalities.
User Impact
(Optional) Describe the impact of this issue on your use of the Trio app. Include any specific examples or data that demonstrate how widespread or severe the problem is.
Is your feature request related to a problem? Please describe.
If people make the slightest changes to their builds, the commit ID will not show where they are in terms of syncing with Trio upstream. If we add parent commit refs to the build details displayed at the top of Settings view, we will probably be able to se recent merges with Trio main/dev/alpha as parent commits.
Describe the solution you'd like
Make minor adjustments to the current code for getting and displaying build details
Describe alternatives you've considered
List and describe any alternative solutions or features you've considered that could also address the problem. Explain why you believe the proposed solution is the best option.
Additional context
Include any other context, screenshots, or relevant information that might help in understanding the issue or the proposed solution. If applicable, describe any previous discussions or decisions that relate to this feature request.
Technical Details
If applicable, provide any technical details or considerations that might impact the implementation of this feature. This could include dependencies, potential risks, or required changes to existing functionalities.
User Impact
(Optional) Describe the impact of this issue on your use of the Trio app. Include any specific examples or data that demonstrate how widespread or severe the problem is.