sbt / sbt/sbt-pull-request-validator
Not traversing dependencies between projects
Nobody has claimed this yet.
- Dominant language
- Scala
- Stars
- 25
- Forks
- 9
- Avg merge
- 11h 21m
- Merged PRs (30d)
- 4
Description
For example, in Akka, we have akka-actor-tests -> akka-testkit -> akka-actor and one would expect a change in akka-actor to trigger build in akka-actor-tests. It doesn't because we have not explicitly defined the dependency from akka-actor-tests to akka-actor, but it's via akka-testkit.
Would be nice if it would notice such dependencies automatically.
Not a critical issue for us, since the workaround is simply to add an additional explicit dependency from akka-actor-tests to akka-actor.
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
The issue names no files, tests, or entry points. Start by tracing how project dependencies are discovered and how changed projects are selected for validation; compare the explicit akka-actor-tests dependency workaround with the transitive akka-testkit relationship. Done means a dependency change is detected through that chain and triggers validation of the dependent project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- build-system
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100