search

kiegroup / github-action-build-chain

86 stars 24 forks source link

Log commit hash while describing checkout/merge #199

Open danielezonca opened 2 years ago

danielezonca commented 2 years ago

At the moment in the log it is not possible to understand the exact commit that has been used for the build

[INFO]  [kiegroup/kogito-runtimes] Checking out project
[INFO]  [kiegroup/optaplanner] Checking out project
...
[INFO]  [kiegroup/optaplanner] Rebasing https://github.com/danielezonca/optaplanner:KOGITO-6236-fix-kogitoobjectmapper onto https://github.com/kiegroup/optaplanner:main
[INFO]  [kiegroup/kogito-runtimes] Rebasing https://github.com/danielezonca/kogito-runtimes:KOGITO-6236-fix-kogitoobjectmapper onto https://github.com/kiegroup/kogito-runtimes:main

I think it should be useful to have commit hash in the log for each branch

Rebasing https://github.com/danielezonca/kogito-runtimes:KOGITO-6236-fix-kogitoobjectmapper 19ea3dd onto https://github.com/kiegroup/kogito-runtimes:main eba77d0

The main reason is that when you have multi repo PRs and you push commits on more repos the build starts immediately and you might not know exactly what it is cloning/compiling

danielezonca commented 2 years ago

@Ginxo Wdyt? ^

Ginxo commented 2 years ago

you absolutely right. Let's do it!