Skip to content

Commit

Permalink
Create SECURITY.md
Browse files Browse the repository at this point in the history
  • Loading branch information
Coloroflaw authored Nov 11, 2024
1 parent 5b7bcd7 commit feab442
Showing 1 changed file with 35 additions and 0 deletions.
35 changes: 35 additions & 0 deletions SECURITY.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,35 @@
We welcome contributions from developers of all skill levels!

Who can contribute?

Anyone with an interest in web development and a desire to improve the Wix Code Injector extension can contribute.

How can I contribute?

Here are some ways you can contribute:

Bug reports: If you encounter a bug while using the extension, please report it by creating a new issue on the GitHub repository. Be sure to include clear and concise information about the bug, including steps to reproduce it.
Feature requests: Do you have an idea for a new feature that would improve the extension? Submit a feature request in the GitHub repository. Describe your proposed feature in detail, explaining how it would benefit users.
Code contributions: We welcome pull requests that fix bugs, add new features, or improve the existing codebase. Before submitting a pull request, please ensure you have reviewed the following guidelines:
Fork the repository: Create a fork of the Wix Code Injector repository on GitHub.
Create a branch: Create a new branch for your changes.
Write clean code: Follow the existing code style and formatting conventions.
Test your changes: Make sure your changes don't introduce any regressions.
Submit a pull request: Submit a pull request with a clear description of your changes.
Documentation: Help improve the documentation for the extension. This could include creating new guides, updating existing documentation, or fixing typos.
Coding Style:

We follow a consistent coding style to improve code readability and maintainability. Please make sure your code adheres to the existing style guide before submitting a pull request. You can find the style guide document in the repository (if available) or use a linter like ESLint to ensure consistent formatting.

Testing:

We encourage all contributors to write unit tests for their changes. This helps ensure that the extension remains functional after modifications.

Communication:

If you have any questions about contributing, feel free to reach out to the maintainers of the extension through GitHub issues or discussions. We are happy to help!

Additional Resources:

GitHub Forking Guide: https://docs.github.com/articles/fork-a-repo
How to Create a Pull Request on GitHub: https://www.activepieces.com/blog/github-pull-requests-to-google-docs

0 comments on commit feab442

Please sign in to comment.