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

Look for .starscope.json in current dir before falling back to home folder. #181

Merged
merged 1 commit into from
Sep 11, 2020
Merged

Look for .starscope.json in current dir before falling back to home folder. #181

merged 1 commit into from
Sep 11, 2020

Conversation

bry-guy
Copy link

@bry-guy bry-guy commented Sep 11, 2020

This PR supports configuring a .starscope.json on a per-directory basis. This resolves #180.

@eapache
Copy link
Owner

eapache commented Sep 11, 2020

Thanks!

I think it makes sense to accept this patch anyway, but I also wanted to point out that you can already specify exclusions per-project on the command line during the initial database build, and they will be persisted (i.e. you don't need to specify them every time you update/export the DB).

@eapache eapache merged commit daaab71 into eapache:master Sep 11, 2020
@eapache
Copy link
Owner

eapache commented Sep 11, 2020

#142 is also related. This PR doesn't fully address it, but it moves us closer in that direction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow specifying .starscope.json config files on a per-directory basis
2 participants