-
Notifications
You must be signed in to change notification settings - Fork 49
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
pinto pull <list_of_modules produces erroneous "pinto log" entry #86
Comments
There has been some slight improvement here. Pinto now dedupes and sorts the list of targets in the commit message. But it doesn't yet filter out the ones that were actually pulled. That is doable though. |
This is an attempt to fix GH #86. The goal was to just remove targets from the log message that have already been pulled. But this turns out to be more complicated because you might pull a target just to register its prereqs, even though the target itself is already registered. So now, the message is reduced to the fewest possible targets, removing those that were not affected by the operation unless one of it's prereqs was affected. However, it's not perfect. Sometimes you really want that target in the list, or you may be confused about why it isn't there. To avoid confusion, I've added a warning about pulling targets that are already on the stack.
[BUG FIXES] - Fixed behavior of the --force flag on the new "update" command. It now applies to all packages that might be updated, not just the targets list on the command line. [ENHANCEMENTS] - When generating the title for the log message, only the targets at the top of the dependency graph are listed, and only if they (or one of their prerequisites) were actually affected by the operation. In effect, redundant and prereq targets are therefore excluded from the message. This attempts to fix GH #86. Thanks @akarelas.
I think I've fixed this as much as I can. There's no way for Pinto to always know exactly which targets should appear in the commit message. So it tries to make a best guess based on which targets actually caused the stack to change. |
I have this list of modules in a text file:
I do a
pinto pull <list_of_modules
, and all 4 modules appear in a singlepinto log
entry. So far so good.When I append the following two lines to my
list_of_modules
file, however:...and then
pinto pull <list_of_modules
again, I get the following new erroneous log entry (erroneous because it repeats the modules which were pulled in step 1):The text was updated successfully, but these errors were encountered: