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

Consider adding "discard-changes": true #495

Closed
joelpittet opened this issue Jun 20, 2019 · 2 comments
Closed

Consider adding "discard-changes": true #495

joelpittet opened this issue Jun 20, 2019 · 2 comments
Assignees
Labels
Quick fix State: Confirmed The issue was triaged and confirmed for development Type: Feature Issue is a new feature request

Comments

@joelpittet
Copy link
Contributor

joelpittet commented Jun 20, 2019

By adding this:

"config": {
    "discard-changes": true
}

You can have your build tools use -n flag without leaving dirty changes around.
https://getcomposer.org/doc/06-config.md#discard-changes

I can't think of a situation where you'd like to keep this as the default false so I'm proposing it be added to this.

@leymannx
Copy link
Collaborator

Ah yes, I think now I understand. "discard-changes": true will only be taken into account when running the command with the --no-interaction option (or -n flag). That makes sense.

@AlexSkrypnyk
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Quick fix State: Confirmed The issue was triaged and confirmed for development Type: Feature Issue is a new feature request
Projects
None yet
Development

No branches or pull requests

3 participants