If you'd like to contribute to this repository, please read the following guidelines. Contributors are more than welcome to share your learnings with others from centralized location.
Code of Conduct
Question or Problem?
Please do not open GitHub issues for general support questions as the GitHub list should be used for feature requests and bug reports. This way we can more easily track actual issues or bugs from the code and keep the general discussion separate from the actual code.
If you have questions about list formatting, feel also free to use following channels for having an open discussion with the community and engineering.
- SharePoint Developer Space at http://techcommunity.microsoft.com
- SharePoint Stack Exchange with 'spfx' tag
Typos, Issues, Bugs and contributions
Whenever you are submitting any changes to the SharePoint repositories, please follow these recommendations.
- Always fork repository to your own account for applying modifications
- Do not combine multiple changes to one pull request, please submit for example any samples and documentation updates using separate PRs
- If you are submitting multiple samples, please create specific PR for each of them
- If you are submitting typo or documentation fix, you can combine modifications to single PR where suitable
Submitting changes as pull requests
Here's a high level process for submitting new samples or updates to existing ones.
- Sign the Contributor License Agreement (see below)
- Fork the main repository to your GitHub account
- Create a new branch for your fork for the contribution based on dev branch
- Include your changes to your branch
- Commit your changes using descriptive commit message - These are used to track changes on the repositories for monthly communications, see October 2017 as an example
- Create a pull request in your own fork and target 'master' branch
- Fill up the provided PR template with the requested details
note. Delete the feature specific branch only AFTER your pull request has been processed.
Sample naming and structure guidelines
When you are submitting a new sample, it has to follow up below guidelines
- You will need to have a README file for your sample, which is based on provided template under the Samples folder. Please copy this template and update accordingly. README has to be named as README.md with capital letters.
- You will need to have a picture of the sampe in practice in the README file ("pics or it didn't happen"). Preview image must be located in the sample folder and should be named as screenshot.png.
- README template contains specific tracking image as a final entry in the page with img tag by default to https://telemetry.sharepointpnp.com/sp-dev-list-formatting/samples/readme-template. This is transparent image, which is used to track popularity of individual samples in GitHub.
- Updated the image src element according with repository name and folder information. If your sample is for example in samples folder and named as date-range-format, src element should be updated as https://telemetry.sharepointpnp.com/sp-dev-list-formatting/samples/date-range-format
- When you are submitting new sample solution, please name the sample solution folder accordingly
- Folder name should start by identifying type of the field or data which sample is for - like "number-", "text-", "date-", "image"
- If sample can be used on any field type, please use "generic-" as the prefix for your sample folder
- Do not use words "sample", "field", "column", "row", "view" in the folder name
- Do not use period/dot in the folder name of the provided sample
Step-by-step on submitting a pull request to this repository
Please see following wiki post from the GitHub repository wiki for exact steps on submitting new pull requests.
- How to submit a PR to SharePoint repository? - Work in progress
Signing the CLA
Before we can accept your pull requests you will be asked to sign electronically Contributor License Agreement (CLA), which is prerequisite for any contributions to PnP repository. This will be one time process, so for any future contributions you will not be asked to re-sign anything. After the CLA has been signed, our PnP core team members will have a look on your submission for final verification of the submission. Please do not delete your development branch until the submission has been closed.
You can find Microsoft CLA from the following address - https://cla.microsoft.com.
Thank you for your contribution.
Sharing is caring.