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

Document top-level files option #105

Open
sindresorhus opened this issue Apr 19, 2016 · 2 comments
Open

Document top-level files option #105

sindresorhus opened this issue Apr 19, 2016 · 2 comments
Labels
💵 Funded on Issuehunt This issue has been funded on Issuehunt help wanted

Comments

@sindresorhus
Copy link
Member

sindresorhus commented Apr 19, 2016

Issuehunt badges

First needs to make sure it actually works. We already have files in overrides. Would be nice to be able to use it in the top-level config too instead of using CLI arguments. Should also write a test to prevent future regressions.

There is a $10.00 open bounty on this issue. Add more on Issuehunt.

@IssueHuntBot
Copy link

@issuehuntfest has funded $10.00 to this issue. See it on IssueHunt

@elyager
Copy link

elyager commented Feb 13, 2019

This issue seems to be from a long time ago, is this still required or have been already implemented?

I've been reading the code but I don't fully understand this request:

Would be nice to be able to use it in the top-level config too instead of using CLI arguments.

What CLI argument are you referring to?

What is the top-leve config? (do you mean the files on config directory?)

I'm a little bit lost...

@issuehunt-oss issuehunt-oss bot added the 💵 Funded on Issuehunt This issue has been funded on Issuehunt label May 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
💵 Funded on Issuehunt This issue has been funded on Issuehunt help wanted
Projects
None yet
Development

No branches or pull requests

3 participants