Daniel Müller 3a2088e347 Log more comprehensive commit information after checkout ... After checkout, the action currently logs the SHA-1 of the top most commit. There are cases when this information is not very telling, though. Consider the case of some automation that applies one or more commits on top of what the repository already contained. If something like this happens, the SHA-1 may be meaningless to the user. Given that this information is unlikely to be programmatically evaluated, we may as well include a bit more than only the commit SHA-1, in the hopes that it provides some more useful information to the user. To that end, this change proposes logging not just the SHA-1, but also the commit summary. At the very least that gives a user a straw what to look for if the commit is indeed not available locally, in the best case we end up with a message about a merge commit, that helps users glean information about the base commit as well: > e0dcaaee9063ab55ffe2e0c8dcffb4a9611208f9 Merge e3aafdc7d10cf5002e39c5d4fe867d1b27d0ff7b into b77ffb30cfc5f58e957571d8541c6a7e3da19221		2022-07-19 15:35:29 -07:00
..
index.js	Log more comprehensive commit information after checkout	2022-07-19 15:35:29 -07:00
problem-matcher.json	Convert checkout to a regular action (#70)	2019-12-03 10:28:59 -05:00