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
Seems likely [timestamp] should actually be a timestamp, but when butler deploys to github pages, the commit message is always: Updated with Butler - [timestamp]
While we're in that area of the code, it would also be handy to have the commit hash and message of the branch the deploy is working from. You can get this with git log -1 --format="[%ai] %h: %s" So if we were deploying from here:
The commit message would be: Updated with Butler - [2016-09-13 14:28:49 -0500] d23a459: create breadcrumb component
This suggestion means we get the timestamp of the recent commit, and not the timestamp of the commit which triggers the deployment, but the timestamp of the commit triggering the deployment is already in the commit. If we have the commit log, we probably already have that timestamp.
The text was updated successfully, but these errors were encountered:
Seems likely [timestamp] should actually be a timestamp, but when butler deploys to github pages, the commit message is always:
Updated with Butler - [timestamp]
While we're in that area of the code, it would also be handy to have the commit hash and message of the branch the deploy is working from. You can get this with
git log -1 --format="[%ai] %h: %s"
So if we were deploying from here:The commit message would be:
Updated with Butler - [2016-09-13 14:28:49 -0500] d23a459: create breadcrumb component
This suggestion means we get the timestamp of the recent commit, and not the timestamp of the commit which triggers the deployment, but the timestamp of the commit triggering the deployment is already in the commit. If we have the commit log, we probably already have that timestamp.
The text was updated successfully, but these errors were encountered: