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

Update .gitignore #295

Merged
merged 1 commit into from
Oct 8, 2022
Merged

Update .gitignore #295

merged 1 commit into from
Oct 8, 2022

Conversation

LoipesMas
Copy link
Contributor

.gitignore was matching src/huak/env folder, so I re-included it.
Alternatively we could make venv dir matching more specific (e.g. only match them in root directory and/or huak-py). Should be fine either way.
Or we could remove matching env/ altogether, because pretty much no one uses that AFAIK ;)
Let me know what would you prefer!

@LoipesMas LoipesMas changed the title Unignore src/huak/env` Unignore src/huak/env Oct 8, 2022
@cnpryer
Copy link
Owner

cnpryer commented Oct 8, 2022

Woah how didn't I notice this?

@cnpryer
Copy link
Owner

cnpryer commented Oct 8, 2022

Curious how it hasn't been an issue.

@cnpryer
Copy link
Owner

cnpryer commented Oct 8, 2022

This is a dumb nit, but couldn't we just do

/env/

@LoipesMas
Copy link
Contributor Author

Curious how it hasn't been an issue.

I think it was added quite recently and git seems fine with changing ignored files, but won't register new ones.

@cnpryer
Copy link
Owner

cnpryer commented Oct 8, 2022

My only problem with this really is that if the project structure ever changes we'd have to update that line, right?

@LoipesMas
Copy link
Contributor Author

This is a dumb nit, but couldn't we just do

/env/

That's what I meant by making it more specific. This wouldn't work if someone had env/ in huak-py directory, but it can be handled on individual basis.

My only problem with this really is that if the project structure ever changes we'd have to update that line, right?

Yep

@cnpryer
Copy link
Owner

cnpryer commented Oct 8, 2022

Well I think we can add a .gitignore to huak-py if that's the case (I think) There's already a gitignore in there. I'm just hesitant to hardcode things. If there's a future refactor big enough to impact project structure we'd have to remember to update that line.

@cnpryer
Copy link
Owner

cnpryer commented Oct 8, 2022

I'll merge it, but I'm not sure this is a future-proof change to the gitignore. I think telling it to ignore specifically root level env folders would be.

@LoipesMas
Copy link
Contributor Author

I totally forgot that you can have .gitignore in subdirectories. Since it's also handled there, I'll change it to match root dir only

@LoipesMas
Copy link
Contributor Author

Should I change it for all environment names (venv, .venv, etc.) or just env? And do the same in huak-py/.gitignore?

@cnpryer
Copy link
Owner

cnpryer commented Oct 8, 2022

Hmm. Don't do all. We sometimes have .venv (or venv) in resources for mock projects at the moment. Just env please!

@cnpryer
Copy link
Owner

cnpryer commented Oct 8, 2022

I'm wrong! we have a gitignore there. if you want to do all (but .venv) that'd be great!

@cnpryer
Copy link
Owner

cnpryer commented Oct 8, 2022

This is actually good. It's making me think about this more than I thought I'd need to. I don't think .venv needs to be, but maybe I'm missing something with that too.

@LoipesMas
Copy link
Contributor Author

I think we can safely match only those env dirs that are in root directory and handle other ones in separate .gitignores (as we already do)

@cnpryer
Copy link
Owner

cnpryer commented Oct 8, 2022

Thanks!

@cnpryer cnpryer changed the title Unignore src/huak/env Update .gitignore Oct 8, 2022
@cnpryer cnpryer merged commit 85e5543 into cnpryer:master Oct 8, 2022
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.

None yet

2 participants