[Improvement][CI] move the CI action to contributor‘s repo
- Dominant language
- Java
- Stars
- 3.2k
- Forks
- 935
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 298
Description
### What would you like to be improved?
When I pull a request, It will run some github action test to verify the code.
But now this action is running on apache repo. If the contribute doesn't have the repo access, he can't re-run job ( like timeout issue).
### How should we improve?
How about we move some action to contributor's repo
Contributor guide
Research direction
Review the repository's GitHub Actions workflows and determine which pull-request jobs currently run in the Apache repository. Check how contributor-owned repositories, permissions, secrets, and reruns would affect the proposed arrangement. Done means a documented, maintainable CI design that allows contributors to rerun the relevant jobs without repository access.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100