Skip to content

Latest commit

 

History

History
60 lines (42 loc) · 1.97 KB

File metadata and controls

60 lines (42 loc) · 1.97 KB

Contributing to Pylings

First off, thanks for taking the time to contribute! ❤️

Quick Reference

I want to …

Issues

You can open an issue here. If you're reporting a bug, please include the output of the following commands:

  • py --version
  • ls -la
  • Your OS name and version

Pull Requests

You are welcome to open a pull request, but unless it is small and trivial, please open an issue to discuss your idea first

Opening a pull request is as easy as forking the repository and committing your changes. If you need any help with it or face any Git related problems, don't hesitate to ask for help

It may take time to review your pull request. Please be patient

When updating an exercise, check if its solution needs to be updated.

Adding An Exercise

  • Name the file exercises/yourTopic/yourTopicN.rs.
  • Make sure to put in some helpful links, and link to sections of The Book in exercises/yourTopic/README.md.
  • In the exercise, add a // TODO: … comment where user changes are required.
  • Copy exercises/yourTopic/yourTopicN.rs to backups/yourTopic/yourTopicN.rs
  • Add a solution at solutions/yourTopic/yourTopicN.rs with comments explaining it.
  • Add the metadata for your exercise in the pylings/config/config.toml file.
  • Make sure your exercise runs
  • Open a pull request.

Exercise Metadata

The exercise metadata should contain the following, and be in sorted list:

[exercises]
name = "yourTopicN"
dir = "yourTopic"
hint = """
Multiline is supported

This is more readable than using \n on one continous line
""""