Skip to content
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

Store vendor configs hash, use it to determine if file was changed #55

Closed
samdark opened this issue May 5, 2021 · 2 comments
Closed
Labels
status:ready for adoption Feel free to implement this issue. type:enhancement Enhancement

Comments

@samdark
Copy link
Member

samdark commented May 5, 2021

In order to improve experience we can store config hash in a file similar to composer.lock and then use it to determine if there were changes in vendor config. The goal is not to display any warnings if config is a custom one and vendor did not change since last time.

@samdark samdark added status:ready for adoption Feel free to implement this issue. type:enhancement Enhancement labels May 5, 2021
@samdark
Copy link
Member Author

samdark commented May 5, 2021

Alternatively it could be stored as a key in merge plan.

@samdark
Copy link
Member Author

samdark commented May 5, 2021

See #44 (comment). Likely we can avoid it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:ready for adoption Feel free to implement this issue. type:enhancement Enhancement
Projects
None yet
Development

No branches or pull requests

2 participants