Feature Request - Dev Build Header Populates Commit SHA about t3 HOT 6 OPEN

this is gonna be difficult to achieve until we bite the CI bullet :)

It shouldn't be too complicated with the code part, but it make much more sense to then have the whole package pushed embedding the change in code (otherwise we'll have to deal w/ a LOT of maintainance commits).

i drafted the "pop the action" + replace part (reference the commit_id there is as trivial as $env:GITHUB_COMMIT_SHA) here : https://github.com/ylmrx/t3/blob/dev/.github/workflows/dotnet-desktop.yml

executed as: https://github.com/ylmrx/t3/actions/runs/7863244025/job/21453637444

(ps: as you most likely expect, and thus minimal at our scales, this might require a few bucks/month toward github too (worth it imho, but i have no idea about their pricing))

from t3.

I am not really sure. I think there are probably prebuild-scripts for MS-build to achieve this.

from t3.

The example i'm showing in comment above is 95% the default prebuilt-script from github-actions.

also cf.
https://github.com/microsoft/github-actions-for-desktop-apps?tab=readme-ov-file#versioning
(linked in yml header)

from t3.

I think the current solution of the "build-standalone" solution is going to be obsolete as soon as we switch to the main branch.
We then should look in to CI/CD again.

from t3.

Great i look forward to the next iteration of the branch .. that solves the build standalone paradigm

from t3.

Solving this issue in the main branch going forward could easily be achieved by Adding the aft requested
"About" option to the UI for the splash screen and or populate with version number in header

from t3.