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 allow .castor directory as alternative to castor #349

Closed
ruudk opened this issue Mar 28, 2024 · 2 comments · Fixed by #361
Closed

Consider allow .castor directory as alternative to castor #349

ruudk opened this issue Mar 28, 2024 · 2 comments · Fixed by #361

Comments

@ruudk
Copy link
Contributor

ruudk commented Mar 28, 2024

For example, GitHub follows this with .github folder.

Makes it clear it's not related to the project.

@lyrixx
Copy link
Member

lyrixx commented Mar 29, 2024

We changed to castor at the very beginning. I was not really convinced...

I prefer .castor too!

I'll see what I can do if the core team is okay with this move

@pyrech
Copy link
Member

pyrech commented Mar 29, 2024

Both have pros and cons.

But as we will soon have a .castor directory when using remote import, I think it's fair to look natively for tasks in the .castor directory too 👍. I think we can support both naming out of the box.

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 a pull request may close this issue.

3 participants