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
As a developer it will be helpful to know what version of Chirps an end-user is running when triaging issues. Users may have simply cloned main and started running the application - which may have multiple changes that could be the culprit. By bumping the build number (0.1.) on each push to main, developers will be able to cross-reference the commit log to help in any triage.
This Stack Overflow question has a viable solution on how to implement this functionality using a GitHub Action.
The text was updated successfully, but these errors were encountered:
As a developer it will be helpful to know what version of Chirps an end-user is running when triaging issues. Users may have simply cloned
main
and started running the application - which may have multiple changes that could be the culprit. By bumping the build number (0.1.) on each push tomain
, developers will be able to cross-reference the commit log to help in any triage.This Stack Overflow question has a viable solution on how to implement this functionality using a GitHub Action.
The text was updated successfully, but these errors were encountered: