@kcne commented on this pull request.


>  
-```
+1. **Find an Issue**: Browse our 
[issues](https://github.com/openstreetmap/openstreetmap-website/issues) or 
identify a bug/feature you'd like to work on
+2. **Fork & Clone**: Fork the repository and clone it to your local machine
+3. **Set Up**: Follow the [installation guide](INSTALL.md) to set up your 
development environment
+4. **Develop**: Make your changes following our [code quality 
guidelines](#code-quality-guidelines)
+5. **Test**: Write tests for your changes and ensure all existing tests pass
+6. **Commit**: Write clear commit messages following our 
[guidelines](#committing)
+7. **Submit a Pull Request**: Create a pull request with a clear description 
of your changes
+
+## Code Quality Guidelines
+
+### Coding Style
+
+We use [Rubocop](https://github.com/rubocop-hq/rubocop) (for ruby files) and 
[ERB Lint](https://github.com/Shopify/erb-lint) (for erb templates) to help 
maintain consistency in our code. You can run these utilities during 
development to check that your code matches our guidelines:

Added eslint as well. Thanks.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/pull/6111#discussion_r2250064459
You are receiving this because you are subscribed to this thread.

Message ID: 
<openstreetmap/openstreetmap-website/pull/6111/review/3082292...@github.com>
_______________________________________________
rails-dev mailing list
rails-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/rails-dev

Reply via email to