-
-
Notifications
You must be signed in to change notification settings - Fork 398
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
How to set up a local dev environment #34
Comments
I use virtualbox and vagrant pretty heavy when it comes to these kind of project. You can see my Vagrantfile here: Spoiler alert: it's linked to my exercism repo where I also keep my works. |
@mayppong You use this when setting up exercism/xelixir to submit patches to the repository? |
I'm not currently working on any patches for xelixir. I'm only taking the exercises right now. I think it's functionally the same though, between developing the exercises or taking them. I don't see why a new developer wanting to write a new exercise for xelixir can't use this. |
Yepp, cool. I'll leave the issue open so that the elixir track maintainers can take a look. Thanks! |
No problem! Please let me know if the maintainer would like me to clean this up and submit it as a PR as well. I'd be happy to do that if they see value in it. |
Does @parkerl's Pull Request finish this issue? The Edit I am happy to add to it if there are additional requirements. |
I think it does address it. I'll close this--let's reopen it if there are specific suggestions for improvement or specific things that seem unclear. |
See issue exercism/exercism#2092 for an overview of operation welcome contributors.
Provide instructions on how to contribute patches to the exercism test suites
and examples: dependencies, running the tests, what gets tested on Travis-CI,
etc.
The contributing document
in the x-api repository describes how all the language tracks are put
together, as well as details about the common metadata, and high-level
information about contributing to existing problems, or adding new problems.
The README here should be language-specific, and can point to the contributing
guide for more context.
From the OpenHatch guide:
The text was updated successfully, but these errors were encountered: