search

dantleech / what-changed

Generate change reports when you update composer
MIT License
118 stars 2 forks source link

Automatically remove archives #8

Closed dantleech closed 5 years ago

dantleech commented 5 years ago

e.g. set max number of archives to 50 or similar, should be configurable.

Nemo64 commented 5 years ago

If the project is in git you could also ask git for the old composer.lock. Then you wouldn't need that archive at all and anyone could look at the changes caused by someone elses update.

dantleech commented 5 years ago

Only if you commit the changelock (and use GIT). But indeed there are a number of strategies.

dantleech commented 5 years ago

Also, it archives the lock file before it updates, so you always get the changes. We could even not create an archive at all, but currently there is some benefit of checking (or re-checking) the changed log after running the update.

dantleech commented 5 years ago

This is redundant now, we no longer archive lock files, we just keep the old one.