This document will help answer common questions and guide you through the steps to make first contribution.
Head to the Issues view in order to report any bug, feature request or share any thought about paths for improvement. The issue will be the main place for discussion.
- Check that the issue has not already been reported
- Use a descriptive title, be clear and concise.
- Include the release version
- Include any additional info such as error messages, CLI args used, configuration parameters, etc.
Please use forks for any code contribution
Markdownlint follows a forking workflow, and we have a simple process for contributions:
- Open an associate issue
- Use forks for any code
contribution:
- Fork the project
If you're adding or making changes to rules, read the Development docs
- Follow the forking workflow
steps:
- Fork the project ( https://github.com/EOSC-synergy/sqaaas-web/fork )
- Create a branch (
git checkout -b my-contribution
)- Branch name might be prefixed to indicate whether the contribution is a feature or bugfix
- Commit your changes (
git commit -am 'Add some feature'
) - Push to branch to your fork (
git push origin my-new-feature
)
- Create a GitHub Pull Request for your contribution