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.

Sign up for GitHub

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

Jump to bottom

Make a dirty working tree warn, not error #3550

Open
hdgarrood opened this issue Mar 4, 2019 · 0 comments
Open

Make a dirty working tree warn, not error #3550

hdgarrood opened this issue Mar 4, 2019 · 0 comments
Labels
purs publish

Comments

@hdgarrood
Copy link
Contributor

See e.g. purescript/purescript-foreign-object#5

We should also reproduce the output of git status in the warning text so that you can see which files are actually causing the warning; this would be especially useful in the case of CI builds.

I expect @garyb will be in favour of this; are there any objections?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
purs publish
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hdgarrood