Contributing to this repository
Last updated
Was this helpful?
Last updated
Was this helpful?
Have you read the ?
Check out the and see what are accepted.
If you spot something new, open an issue using a . We'll use the issue to have a conversation about the problem you want to fix.
Now that you're a part of the community, you can keep participating in many ways.
Learn more about contributing:
You can contribute to the repository several ways.
Labels can help you find an issue you'd like to help with.
Fork using the command line:
After that, we may have questions, check back on your PR to keep up with the conversation.
Congratulations! The whole Intel community thanks you.
Every single PR is reviewed.
Reviews are always respectful, acknowledging that everyone did the best possible job with the knowledge they had at the time.
Reviews discuss content, not the person who created it.
Reviews are constructive and start conversation around feedback.
You should always review your own PR first.
For content changes, make sure that you:
are used to track tasks that contributors can help with. If an issue has no labels, we haven't reviewed it yet and you shouldn't begin work on it.
If you've found something in the content or the website that should be updated, search open issues to see if someone else has reported the same thing. If it's something new, open an issue using a . We'll use the issue to have a conversation about the problem you want to fix.
A is a way to suggest changes in the repository.
You can browse to find something that needs help.
If you find something that is not present in the issues section
The is for problems or updates that anyone in the community can start working on.
Check all available labels with description .
so that you can make your changes without affecting the original project until you're ready to merge them.
Make your changes to the file(s) you'd like to update. Here are some tips and tricks for .
When you're done making changes and you'd like to propose them for review. Read if unsure how to do it.
Once you submit your PR, others from the core team will review it with you. The first thing you're going to want to do is a .
Did you have an issue, like a merge conflict? Check out our on how to resolve merge conflicts and other issues.
Once your PR is merged, you will be listed as a contributor in the .
We may ask for changes to be made before a PR can be merged, either using or pull request comments. You can apply suggested changes directly through the UI. You can make any other changes in your fork, then commit them to your branch.
As you update your PR and apply changes, mark each conversation as .
To work with in the repository the following should be fulfilled.