-
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update commits do not provide a helpful diff #3
Comments
Agreed that'd be better, here's where |
Maybe adding |
base branch for the automatic PR is already main: |
Yeah, the action notes that actions which checkout a commit may require |
working on |
this means that the diff of the PR is always against Wouldn't it make sense to have the action work on |
tbh haven't dug into git submodules enough to understand what happens when the same submodule is added more than once agree the generic commit force-pushing without merging is hacky/unideal |
I guess the pull requests for updating the repo commits are automatically generated, and they use a commit that does not have the current head as a parent, so the
.gitmodules
file appears new every time. This means you can't see which repos have been updated. It'd be nice to have a meaningful diff (and history) to be able to know what's changing.Example: https://github.com/PatMyron/cloudformation-resource-providers/pull/1/files#diff-fe7afb5c9c916e521401d3fcfb4277d5071798c3baf83baf11d6071742823584
The text was updated successfully, but these errors were encountered: