kiegroup / kiegroup/github-action-build-chain
Log commit hash while describing checkout/merge
- Dominant language
- TypeScript
- Stars
- 94
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
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
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.