You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
When changing a dependency, I'd like to be informed via PR comment about all the changes that are actually happening in the dependency graph.
The build system I use has a complex logic for resolving transitive dependencies, so I can't always tell what side-effects are applied whenever a dependency is updated.
Describe the solution you'd like
When change in a dependency graph is detected, add a (opt-in?) section to the PR's comment with all changes. This is actually implemented in the action's output (below), my request would be only to append this section to PR's comment.
Describe alternatives you've considered
I thought about intercepting action's output log and filtering Dependency Changes section, but I couldn't find a way to interepct the output in the end
I could use JSON from outputs.dependency-changes, but this requires playing with jq and maintain a parsing logic
Is your feature request related to a problem? Please describe.
When changing a dependency, I'd like to be informed via PR comment about all the changes that are actually happening in the dependency graph.
The build system I use has a complex logic for resolving transitive dependencies, so I can't always tell what side-effects are applied whenever a dependency is updated.
Describe the solution you'd like
When change in a dependency graph is detected, add a (opt-in?) section to the PR's comment with all changes. This is actually implemented in the action's output (below), my request would be only to append this section to PR's comment.
Describe alternatives you've considered
Dependency Changes
section, but I couldn't find a way to interepct the output in the endoutputs.dependency-changes
, but this requires playing withjq
and maintain a parsing logicAdditional context
The build system I use is Gradle, I use
dependency-submission
action: https://github.com/gradle/actions/tree/main/dependency-submissionThe text was updated successfully, but these errors were encountered: