-
Notifications
You must be signed in to change notification settings - Fork 97
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oryx contribution guide #2447
Oryx contribution guide #2447
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we move it to the separate folder smth like "Contribute to Oryx" and also please add a reference to the documenation contribution guide as usially you also need to update a documentation as well https://docs.spryker.com/docs/scos/user/intro-to-spryker/contribute-to-the-documentation/contribute-to-the-documentation.html
- If you’ve added code that should be tested, add tests. | ||
- Ensure all GitHub actions required checks are passed. | ||
- Provide a clear and concise description of your changes in the pull request description. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add information about what happens next. After approving a pull request we will update a reporter with the next steps. Pull request can be rejected, approved or we may ask for some clarification or changes.
Draft of the Oryx contribution guide focused on Composable Storefront (so Fulfillment and other applications are totally missed here).
Code of Conduct and Contributor License Agreement are missing.