spring-cloud / spring-cloud/spring-cloud-github-actions
Release and join workflow should only run in commercial repos
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- Avg merge
- 2h 31m
- Merged PRs (30d)
- 6
Description
All releases, commercial, oss, and hotfixes will always initiate from the commercial repo so the release and join workflows should only ever run from the commercial repo. The user input should not have the option to accept oss repo names and should fail with a clear error message indicating that.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Inspect the release and join workflows and the user-input validation or entry points they use. Confirm how repository names are accepted, then verify that OSS repository names are rejected with a clear error and that both workflows run only from the commercial repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100