spring-projects / spring-projects/spring-security
Support Forks Enabling Workflows
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
All workflows are disabled for forks. It would be nice if in the GitHub repository's settings, a fork could specify which Spring Security workflows it would like to enable.
One way to do this would be to change the workflows to look up the RUN_JOBS environment variable as a secret, though there may be other ways, too.
Contributor guide
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
Start by reviewing the repository's GitHub workflows and fork settings, with the related issue 9701 for context on why workflows are disabled. Define how a fork selects Spring Security workflows to enable, then verify that the selected workflows run while unselected ones remain disabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100