spring-projects / spring-projects/spring-boot
GitHub actions is masking 'ci'
Open
Nobody has claimed this yet.
type: task
- Dominant language
- Java
- Stars
- 81.5k
- Forks
- 42.7k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 65
Description
> Task :spring-boot-project:spring-boot-devtools:checkArchitectureTest
> Task :spring-boot-project:spring-boot-devtools:checkCompileClasspathForProhibitedDependen***es
> Task :spring-boot-project:spring-boot-devtools:checkIntTestCompileClasspathForProhibitedDependen***es
> Task :spring-boot-project:spring-boot-devtools:checkIntTestRuntimeClasspathForProhibitedDependen***es
> Task :spring-boot-project:spring-boot-devtools:checkRuntimeClasspathForProhibitedDependen***es
> Task :spring-boot-project:spring-boot-devtools:checkSpringConfigurationMetadata
> Task :spring-boot-project:spring-boot-devtools:checkTestCompileClasspathForProhibitedDependen***es
> Task :spring-boot-project:spring-boot-devtools:checkTestRuntimeClasspathForProhibitedDependen***es
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 reproducing the shown spring-boot-devtools Gradle task output in GitHub Actions and inspect how the workflow renders those logs. Done means dependency-related task names such as checkCompileClasspathForProhibitedDependencies are displayed without masking.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, java
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100