kiegroup / kiegroup/github-action-build-chain
Replicate actions checkout to check out repositories in build chain
- Dominant language
- TypeScript
- Stars
- 94
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
In #392 we renamed the target branch to source after merging to fix the sonar cloud issue.
I think it will be worthwhile to explore any side effects of this as well as mimic how github checks out repositories in PR just so that if we ever add a new tool like sonar cloud we will have consistent behavior.
Looking at sonarcloud-github-action, their sample workflow shows that simply using actions/checkout and running sonar cloud is enough to get PR analysis[1]. So if we can replicate how action/checkout checks out a repo during a PR we should be able to get what we want.
actions/checkout by default uses GITHUB_SHA to checkout a repository which points to a test merge commit that github produces by merging source into target during a pull request event. So instead of actually cloning and then merging, it simply fetches and checks out a commit.
[1] https://github.com/SonarSource/sonarcloud-github-action#usage
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reviewing issue #392 and the repository's GitHub Actions build-chain entry points, then compare the requested behavior with actions/checkout during pull request events. Done means the build chain consistently checks out the pull request test-merge commit and its side effects are understood.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions, typescript
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100