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
{{ message }}
This repository has been archived by the owner on Sep 6, 2021. It is now read-only.
Currently, when we build an installer there's no record of what Git SHA the bits were pulled from. We have to keep track of this manually if we want any record of it (e.g. by tagging and being careful to always generate installers from a fixed tag, and remembering which installers go with which tags).
It'd be much better to have the staging scripts actually create a file on disk that is included in the installer payload, containing a record of which brackets & brackets-shell SHAs were used.
The text was updated successfully, but these errors were encountered:
(Split from #1524 per Peter T)
Currently, when we build an installer there's no record of what Git SHA the bits were pulled from. We have to keep track of this manually if we want any record of it (e.g. by tagging and being careful to always generate installers from a fixed tag, and remembering which installers go with which tags).
It'd be much better to have the staging scripts actually create a file on disk that is included in the installer payload, containing a record of which brackets & brackets-shell SHAs were used.
The text was updated successfully, but these errors were encountered: