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.
Today one can use the changed subsystem to have Pants inspect git and list targets that have changed. One might use this in CI today to only run tests of targets that have changed since a main branch, or only build docker images that
I'd like a companion that instead of giving the boolean 'did it change?' lists the commits. I imagine using this as input to release related systems such as:
"Hey you are about to deploy X, this is what changed since the last deploy"
Some dashboard along the lines of deployment frequency that would have pending changes. (ex: Does service X from team Y have $LARGE_NUMBER of changes waiting to be released.)
Describe the solution you'd like
Some sort of "what changed" goal(?) that would take:
Since commit
Transitive Y/N
Targets(s)
Pass along some git formatting options
And return a list of commits
Describe alternatives you've considered
I could probably glue together some sort of bash-y script to do this.
Where there is a current mechanism along the lines of git log <previous_release>..HEAD --oneline --pretty=format:"* %s" -- <path to individual service> that one could imagine looking something like pants --changed-since=HEAD release_notes app/<service>::.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Today one can use the changed subsystem to have Pants inspect git and list targets that have changed. One might use this in CI today to only run tests of targets that have changed since a
main
branch, or only build docker images thatI'd like a companion that instead of giving the boolean 'did it change?' lists the commits. I imagine using this as input to release related systems such as:
Describe the solution you'd like
Some sort of "what changed" goal(?) that would take:
And return a list of commits
Describe alternatives you've considered
I could probably glue together some sort of bash-y script to do this.
Additional context
Related Slack thread regrading release notes: https://pantsbuild.slack.com/archives/C046T6T9U/p1725634209269079
Where there is a current mechanism along the lines of
git log <previous_release>..HEAD --oneline --pretty=format:"* %s" -- <path to individual service>
that one could imagine looking something likepants --changed-since=HEAD release_notes app/<service>::
.The text was updated successfully, but these errors were encountered: