Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show Platform build number in Paratext builds #1393

Open
Sebastian-ubs opened this issue Dec 13, 2024 · 0 comments
Open

Show Platform build number in Paratext builds #1393

Sebastian-ubs opened this issue Dec 13, 2024 · 0 comments
Labels
enhancement New feature or request ux UX design needed

Comments

@Sebastian-ubs
Copy link
Contributor

User Story

As a developer I need to know which version of Platform a user is running so that I can find and fix the root cause of an issue.

Description

Get the commit numbers from all repositories that are pulled into the Paratext 10 Studio build and list them as part of the version in the about dialog. Also write them to a file, so that even when Paratext is not starting it can be retrieved.

Background

The about dialog of Paratext 10 Studio shows the commit from the https://github.com/paranext/paratext-10-studio/ repository (which is very good).
Image
However the Paratext 10 Studio build also pulls in the latest code (at build time) on main from

Therefore, to identify the software state, the included commit numbers from these repositories are needed as well.
e.g. see that in between #28, #29 and #30 the build number is unchanged, because no Paratext specific change was done in the PT10S repository.
Image
Image
Image

Implementation idea

Testing ideas

@Sebastian-ubs Sebastian-ubs added enhancement New feature or request ux UX design needed labels Dec 13, 2024
@Sebastian-ubs Sebastian-ubs moved this to 📥 For Consideration in Paranext Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request ux UX design needed
Projects
Status: 📥 For Consideration
Development

No branches or pull requests

1 participant