First off, thanks for taking the time to contribute! 🚀
All types of contributions are encouraged and valued. See the Table of Contents for different ways to help and details about how this project handles them. Please make sure to read the relevant section before making your contribution. It will make it a lot easier for us maintainers and smooth out the experience for all involved. The community looks forward to your contributions.
And if you like the project, but just don't have time to contribute, that's fine. There are other easy ways to support the project and show your appreciation, which we would also be very happy about:
- Star the project
- Tweet about it
- Refer this project in your project's readme
- Mention the project at local meetups and tell your friends/colleagues
- Code of Conduct
- I Have a Question
- I Want To Contribute
- Reporting Bugs
- Suggesting Enhancements
- Your First Code Contribution
- Improving The Documentation
- Styleguides
- Commit Messages
This project and everyone participating in it is governed by the Starton Code of Conduct. By participating, you are expected to uphold this code. Please report unacceptable behavior to [email protected].
If you want to ask a question, we assume that you have read the available Documentation.
Before you ask a question, it is best to search for existing Issues that might help you. In case you have found a suitable issue and still need clarification, you can write your question in this issue. It is also advisable to search the internet for answers first.
If you then still feel the need to ask a question and need clarification, we recommend the following:
- Open an Issue.
- Provide as much context as you can about what you're running into.
- Provide project and platform versions (nodejs, npm, etc), depending on what seems relevant.
We will then take care of the issue as soon as possible.
When contributing to this project, you must agree that you have authored 100% of the content, that you have the necessary rights to the content and that the content you contribute may be provided under the project license.
A good bug report shouldn't leave others needing to chase you up for more information. Therefore, we ask you to investigate carefully, collect information and describe the issue in detail in your report. Please complete the following steps in advance to help us fix any potential bug as fast as possible.
- Make sure that you are using the latest version.
- Determine if your bug is really a bug and not an error on your side e.g. using incompatible environment components/versions (Make sure that you have read the documentation. If you are looking for support, you might want to check this section).
- To see if other users have experienced (and potentially already solved) the same issue you are having, check if there is not already a bug report existing for your bug or error in the bug tracker.
- Also make sure to search the internet (including Stack Overflow) to see if users outside of the GitHub community have discussed the issue.
- Collect information about the bug:
- Stack trace (Traceback)
- OS, Platform and Version (Windows, Linux, macOS, x86, ARM)
- Version of the interpreter, compiler, SDK, runtime environment, package manager, depending on what seems relevant.
- Possibly your input and the output
- Can you reliably reproduce the issue? And can you also reproduce it with older versions?
You must never report security related issues, vulnerabilities or bugs including sensitive information to the issue tracker, or elsewhere in public. Instead sensitive bugs must be sent by email to .
We use GitHub issues to track bugs and errors. If you run into an issue with the project:
- Open an Issue. (Since we can't be sure at this point whether it is a bug or not, we ask you not to talk about a bug yet and not to label the issue.)
- Explain the behavior you would expect and the actual behavior.
- Please provide as much context as possible and describe the reproduction steps that someone else can follow to recreate the issue on their own. This usually includes your code. For good bug reports you should isolate the problem and create a reduced test case.
- Provide the information you collected in the previous section.
Once it's filed:
- The project team will label the issue accordingly.
- A team member will try to reproduce the issue with your provided steps. If there are no reproduction steps or no obvious way to reproduce the issue, the team will ask you for those steps and mark the issue as
needs-repro. Bugs with theneeds-reprotag will not be addressed until they are reproduced. - If the team is able to reproduce the issue, it will be marked
needs-fix, as well as possibly other tags (such ascritical), and the issue will be left to be implemented by someone.
This section guides you through submitting an enhancement suggestion for Starton, including completely new features and minor improvements to existing functionality. Following these guidelines will help maintainers and the community to understand your suggestion and find related suggestions.
- Make sure that you are using the latest version.
- Read the documentation carefully and find out if the functionality is already covered, maybe by an individual configuration.
- Perform a search to see if the enhancement has already been suggested. If it has, add a comment to the existing issue instead of opening a new one.
- Find out whether your idea fits with the scope and aims of the project. It's up to you to make a strong case to convince the project's developers of the merits of this feature. Keep in mind that we want features that will be useful to the majority of our users and not just a small subset. If you're just targeting a minority of users, consider writing an add-on/plugin library.
Enhancement suggestions are tracked as GitHub issues.
- Use a clear and descriptive title for the issue to identify the suggestion.
- Provide a step-by-step description of the suggested enhancement in as many details as possible.
- Describe the current behavior and explain which behavior you expected to see instead and why. At this point you can also tell which alternatives do not work for you.
- You may want to include screenshots and animated GIFs which help you demonstrate the steps or point out the part which the suggestion is related to. You can use this tool to record GIFs on macOS and Windows, and this tool or this tool on Linux.
- Explain why this enhancement would be useful to most Starton users. You may also want to point out the other projects that solved it better and which could serve as inspiration.
If you want to contribute to the Starton project by writing code, here are the general steps to follow:
- Make sure you have a GitHub account.
- Fork the repository to your own GitHub account by clicking the "Fork" button in the top-right corner of the repository page.
- Clone your fork to your local machine using Git: git clone https://github.com//.git
- Create a new branch for your changes: git checkout -b my-new-branch
- Make your changes to the code and write tests if necessary. Be sure to follow the coding conventions and styleguides used in the project.
- Commit your changes using the Conventional Commits format and a descriptive commit message that explains the changes you made. See the Commit Messages section for more details.
- Push your branch to your fork on GitHub: git push origin my-new-branch
- Create a pull request (PR) by clicking the "New pull request" button on your fork page. Make sure to explain what your changes are and why they are needed. Reference any related issues or pull requests if applicable.
- Wait for feedback and discussion from the project maintainers. Be prepared to make changes or updates to your code if requested.
- If your PR is accepted, your changes will be merged into the project's main branch. Congratulations, you've made your first contribution to Starton!
Before making your first code contribution, it's recommended to read the project's documentation and familiarize yourself with the codebase. You can also check the project's issue tracker for issues that need help, or discuss with the community on the project's communication channels.
If you have any questions or need help with your code contributions, don't hesitate to ask the project maintainers. They'll be happy to guide you through the process and provide feedback on your work.
Good documentation is essential for helping users understand how to use and contribute to a project. If you notice any issues with the documentation or have suggestions for how it could be improved, we would be grateful for your help.
If you encounter any issues with the documentation, such as missing or inaccurate information, broken links, or unclear instructions, please let us know by opening a new (issue)[https://github.com/starton-io/docs/issues/new] and selecting the "documentation" label.
When reporting a documentation issue, please provide as much information as possible about the problem, including the relevant section of the documentation, the expected outcome, and any error messages or unexpected behavior you encountered.
If you would like to contribute to the documentation, you can do so by submitting a pull request with your proposed changes. Before you get started, please take a moment to review our styleguides for documentation.
To make a contribution:
- Fork the repository and clone it to your local machine.
- Create a new branch for your changes.
- Make your changes to the documentation, following the style guide.
- Commit your changes using a clear and descriptive commit message that follows the Conventional Commits specification.
- Push your changes to your forked repository.
- Open a pull request with a clear description of your changes and why they are necessary.
Our team will review your pull request and work with you to ensure that your changes meet our quality standards before merging them into the main codebase.
We follow the Conventional Commits 1.0.0 specification for commit messages. The commit message should be structured as follows:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
For more information on this convention, you can refer to the official website: https://www.conventionalcommits.org/en/v1.0.0/.
This guide is based on the contributing-gen and modified by Starton. Make your own!