diff --git a/.github/ISSUE_RESPONSES/wrong-author.md b/.github/ISSUE_RESPONSES/wrong-author.md new file mode 100644 index 00000000..a506fbb5 --- /dev/null +++ b/.github/ISSUE_RESPONSES/wrong-author.md @@ -0,0 +1,15 @@ +## Wrong or missing author @mentions + +Thank you for your submission, but you appear to have forgotten to @mention the sample author(s). + +To help increase your chances of getting assistance from the original authors of the sample, you should make sure to @mention the actual authors (and not the repository maintainers). + +Make sure to include the `@` character before the GitHub username so that the author(s) get notified. + +Please note that the sample authors will not get notified about this issue unless you update this issue accordingly. + +You can find the author(s) of each sample in the sample's `README.md`, under **Solution**. + +We'll automatically close this issue in 7 days unless you update the issue. + +For more information on how to create a good issue, refer to our wiki for more information: [How to Create Good Issues](https://github.com/pnp/powerplatform-samples/wiki/How-to-Create-Good-Issues) \ No newline at end of file diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml index a84f0acc..bcd45cd2 100644 --- a/.github/ISSUE_TEMPLATE/config.yml +++ b/.github/ISSUE_TEMPLATE/config.yml @@ -1,11 +1,14 @@ blank_issues_enabled: false contact_links: - - name: SharePoint Developer Documentation - url: https://github.com/SharePoint/sp-dev-docs/issues/new - about: 📚 Issue related to the SharePoint Framework or its documentation? Submit an issue here. - - name: SharePoint StackExchange - url: http://sharepoint.stackexchange.com/ - about: ⁉️ If you have technical questions about the framework, tag your questions with `#spfx`, `#spfx-webparts`, or `#spfx-tooling` here. - - name: Microsoft Tech Community - url: https://techcommunity.microsoft.com/t5/sharepoint-developer/bd-p/SharePointDev - about: ⁉️ Alternatively, submit your technical questions about the framework in the SharePoint Developer group here + - name: Power Apps Community + url: https://powerusers.microsoft.com/t5/Get-Help-with-Power-Apps/ct-p/PA_General + about: Get help from our passionate Power Apps community members. + - name: Power Automate Community + url: https://powerusers.microsoft.com/t5/Get-Help-with-Power-Automate/ct-p/FL_GeneralDiscussions + about: Ask the community members from the Power Automate community. + - name: Power Pages Community + url: https://powerusers.microsoft.com/t5/Get-Help-with-Power-Pages/ct-p/mpp_gethelp + about: It may be the newest family member, but the Power Pages community is one of the most passionate community there is. + - name: Power Virtual Agents Community + url: https://powerusers.microsoft.com/t5/Get-Help-with-Power-Virtual/ct-p/pva_gethelp + about: Ask questions about Power Virtual Agents in the community. \ No newline at end of file diff --git a/.github/ISSUE_TEMPLATE/enhancement.md b/.github/ISSUE_TEMPLATE/enhancement.md index 7868c502..2d38d266 100644 --- a/.github/ISSUE_TEMPLATE/enhancement.md +++ b/.github/ISSUE_TEMPLATE/enhancement.md @@ -1,13 +1,13 @@ --- name: "\U0001F4A1 Suggestion" -about: Suggest an enhancement to make one of our web part samples even better +about: Suggest an enhancement to make one of our Power powerplatform samples even better title: Let's make SAMPLE even better labels: type:enhancement assignees: '' --- -Thank you for your suggestion! Use the sections below to submit a suggestion ONLY if it's related to samples in this repo. If you have an issue or question about the SharePoint Framework or its documentation, please submit it at https://aka.ms/spdev-issues +Thank you for your suggestion! Use the sections below to submit a suggestion ONLY if it's related to samples in this repo. If you have an issue or question about the Power Platform or documentation, please submit it at https://powerusers.microsoft.com/ instead. - Suggestions that do not follow the below template will automatically be closed - All ideas are welcome - let's build something together! diff --git a/.github/ISSUE_TEMPLATE/question.yml b/.github/ISSUE_TEMPLATE/question.yml index 4800f291..2e86420e 100644 --- a/.github/ISSUE_TEMPLATE/question.yml +++ b/.github/ISSUE_TEMPLATE/question.yml @@ -1,5 +1,5 @@ name: ❓ Question -description: Ask a question about one of our web part samples +description: Ask a question about one of our Power Platform samples labels: ['Needs: Triage :mag:', 'type:question'] body: @@ -7,16 +7,16 @@ body: attributes: value: | - Thank you for asking a question! Use the sections below to submit a question ONLY if it's related to samples in this repo. If you have an issue or question about the SharePoint Framework or its documentation, please submit it at https://aka.ms/spdev-issues + Thank you for asking a question! Use the sections below to submit a question ONLY if it's related to samples in this repo. If you have an issue or question about the Power Platform or documentation, please submit it at https://powerusers.microsoft.com/t5/Power-Apps-Community/ct-p/PowerApps1 - Questions that do not follow the below template will automatically be closed - - Don't use questions to diagnose issues with samples, that's what [bug reports](https://github.com/pnp/sp-dev-fx-webparts/issues/new?assignees=&labels=Needs%3A+Triage+%3Amag%3A%2Ctype%3Abug-suspected&template=bug-report.yml) are for! + - Don't use questions to diagnose issues with samples, that's what [bug reports](https://github.com/pnp/powerplatform-samples/issues/new?assignees=&labels=Needs%3A+Triage+%3Amag%3A%2Ctype%3Abug-suspected&template=bug-report.yml) are for! - All questions are welcome - let us know what's on your mind! - This repo is maintained by volunteers. Please be courteous and patient. 🙂 - Remember to include sufficient details and context. - If you have multiple questions please submit them separately so we can track resolution. - Screenshots are always helpful (just paste any images right here in the question) - - If you're trying to start a conversation on a topic, consider using [Discussions](https://github.com/pnp/sp-dev-fx-webparts/discussions). We want to close every issue as quickly as possible, but discussions are intended for longer conversations. + - If you're trying to start a conversation on a topic, consider using [Discussions](https://github.com/pnp/powerplatform-samples/discussions). We want to close every issue as quickly as possible, but discussions are intended for longer conversations. - type: input id: sample @@ -55,7 +55,7 @@ body: validations: required: true name: ❓ Question -description: Ask a question about one of our web part samples +description: Ask a question about one of our Power Platform samples labels: ['Needs: Triage :mag:', 'type:question'] body: @@ -63,10 +63,10 @@ body: attributes: value: | - Thank you for asking a question! Use the sections below to submit a question ONLY if it's related to samples in this repo. If you have an issue or question about the SharePoint Framework or its documentation, please submit it at https://aka.ms/spdev-issues + Thank you for asking a question! Use the sections below to submit a question ONLY if it's related to samples in this repo. If you have an issue or question about the Power Platform or documentation, please submit it at https://powerusers.microsoft.com - Questions that do not follow the below template will automatically be closed - - Don't use questions to diagnose issues with samples, that's what [bug reports](https://github.com/pnp/sp-dev-fx-webparts/issues/new?assignees=&labels=Needs%3A+Triage+%3Amag%3A%2Ctype%3Abug-suspected&template=bug-report.yml) are for! + - Don't use questions to diagnose issues with samples, that's what [bug reports](https://github.com/pnp/powerplatform-samples/issues/new?assignees=&labels=Needs%3A+Triage+%3Amag%3A%2Ctype%3Abug-suspected&template=bug-report.yml) are for! - All questions are welcome - let us know what's on your mind! - This repo is maintained by volunteers. Please be courteous and patient. 🙂 - Remember to include sufficient details and context. diff --git a/.github/ISSUE_TEMPLATE/samplerequest.md b/.github/ISSUE_TEMPLATE/samplerequest.md index e2c2b7d7..158f9aa2 100644 --- a/.github/ISSUE_TEMPLATE/samplerequest.md +++ b/.github/ISSUE_TEMPLATE/samplerequest.md @@ -7,7 +7,7 @@ assignees: '' --- -Thank you for making a request! Use the sections below to submit a request ONLY for a new sample. If you have an issue or question about the SharePoint Framework or its documentation, please submit it at https://aka.ms/spdev-issues +Thank you for making a request! Use the sections below to submit a request ONLY for a new sample. If you have an issue or question about the Power Platform or documentation, please submit it at https://powerusers.microsoft.com/ instead. - Requests that do not follow the below template will automatically be closed - All requests are welcome - the more the merrier! diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md index 84edf864..1f3ebe31 100644 --- a/.github/PULL_REQUEST_TEMPLATE.md +++ b/.github/PULL_REQUEST_TEMPLATE.md @@ -1,10 +1,42 @@ -## This repo does not accept pull requests +> By submitting this pull request, you agree to the [contribution guidelines](https://github.com/pnp/powerplatform-samples/blob/main/CONTRIBUTING.md) -If you have a sample that you'd like to share, please visit the appropriate repository for the type of simple you'd like to provide and look for the **Contribution Guidance** section. +> If you aren't familiar with how to contribute to open-source repositories using GitHub, or if you find the instructions on this page confusing, sign up for one of our [Sharing is Caring](https://pnp.github.io/sharing-is-caring/#pnp-sic-events) events. It's completely free, and we'll guide you through the process. -The following is a list of repositories for each sample types: +> To submit a pull request with multiple authors, make sure that at least one commit is a co-authored commit by adding a `Co-authored-by:` trailer to the commit's message. E.g.: `Co-authored-by: name ` -- [Power Fx Samples](https://github.com/pnp/powerfx-samples) -- [Power Apps Samples](https://github.com/pnp/powerapps-samples) -- [Power Automate Samples](https://github.com/pnp/powerautomate-samples) -- [Power Virtual Agents Samples](https://github.com/pnp/powerva-samples) \ No newline at end of file +> Put an `x` in all the items that apply (`[x]`, without spaces), make notes next to any that haven't been addressed. + +- [ ] Bug fix? +- [ ] New sample? +- [ ] Related issues: fixes #X, partially #Y, mentioned in #Z +- [ ] Needs API permissions? +- [ ] Has other prerequisites? (E.g. requires a list, document library, etc.) + +## What's in this Pull Request? + +> Please describe the changes in this PR. Sample description or details around bugs which are being fixed. +> +> _(DELETE THIS PARAGRAPH AFTER READING)_ + +## Checklist + +> This checklist is mostly useful as a reminder of small things that can easily be forgotten – it is meant as a helpful tool rather than hoops to jump through. +> +> Put an `x` in all the items that apply ([x], no spaces), make notes next to any that haven't been addressed. + +- [ ] My pull request affects only ONE sample. +- [ ] I have updated the README file. +- [ ] My README has at least one static high-resolution screenshot (i.e. not a GIF) +- [ ] My README contains complete setup instructions, including pre-requisites and permissions required + +## Submitter Guidance (DELETE AFTER READING) +> +> *Please update this PR information accordingly. We'll use this as part of our release notes in monthly communications.* +> +> *Pull requests that do not follow this template will be automatically rejected.* +> +> *Please target your PR to `main` branch.* +> +> *Remember that this repository is maintained by community members who volunteer their time to help. Be courteous and patient.* +> +> _(DELETE THIS SECTION AFTER READING)_ diff --git a/.github/label-actions.yml b/.github/label-actions.yml new file mode 100644 index 00000000..249cabfb --- /dev/null +++ b/.github/label-actions.yml @@ -0,0 +1,58 @@ +# Configuration for Label Actions - https://github.com/dessant/label-actions + +# Actions taken when the `incomplete-submission` label is added to issues +status:invalid-issue: + # Post a comment + comment: |+ + Thank you for your submission, but there isn't enough detail in the issue for us to review & move forward. + + The new issue template includes sections for you to fill out. + + Please resubmit your issue and complete the provided sections in the new item template so we can move forward on it refer to our wiki for more information: [How to Create Good Issues](https://github.com/pnp/powerplatform-samples/wiki/How-to-Create-Good-Issues) + + # Close the issue + close: true + +# Actions taken when the `incomplete-submission` label is added to issues +status:incomplete-submission: + # Post a comment + comment: |+ + Thank you for your submission, but there isn't enough detail in the issue for us to review & move forward. + + The new issue template includes sections for you to fill out. Please resubmit your issue and complete the provided sections in the new item template so we can move forward on it refer to our wiki for more information: [How to Create Good Issues](https://github.com/pnp/powerplatform-samples/wiki/How-to-Create-Good-Issues) + + # Close the issue + close: true + +# Actions taken when the `wrong-repo` label is added to issues +status:wrong-repo: + # Post a comment + comment: |+ + Thank you for your submission, but this issues list is intended only for issues related to the samples in this repository. + + For general issues with the Power Platform, you may want to try to post a question in the [Power Platform community](https://powerusers.microsoft.com/). + + # Close the issue + close: true + +# Actions taken when the `wrong-author` label is added to issues +status:wrong-author: + # Post a comment + comment: |+ + ## Wrong or missing contributor @mentions + + Thank you for your submission, but you appear to have forgotten to @mention the sample contributor(s). + + To help increase your chances of getting assistance from the original contributors of the sample, you should make sure to @mention the actual contributors (and not the repository maintainers). + + Please note that the sample contributors will not get notified about this issue unless you update this issue accordingly. + + You can find the contributors of each sample in the sample's `README.md`, under the aptly-named **Contributors** section. + + We'll automatically close this issue in 7 days unless you update the issue. + + For more information on how to create a good issue, refer to our wiki for more information: [How to Create Good Issues](https://github.com/pnp/powerplatform-samples/wiki/How-to-Create-Good-Issues) + + # Close the issue + close: false + diff --git a/.github/workflows/close-stale-issues.yml b/.github/workflows/close-stale-issues.yml new file mode 100644 index 00000000..cf802cc0 --- /dev/null +++ b/.github/workflows/close-stale-issues.yml @@ -0,0 +1,34 @@ +name: "Close stale issues" +on: + schedule: + - cron: "30 1 * * *" + workflow_dispatch: +permissions: + issues: write +jobs: + destale-inator: + runs-on: ubuntu-latest + steps: + - uses: actions/stale@v4 + name: "Close invalid authors" + with: + days-before-issue-stale: 3 + days-before-issue-close: 1 + days-before-pr-stale: -1 + operations-per-run: 1000 + stale-issue-message: "Please note that this issue will be closed within 24 hours because it has been flagged as having invalid authors. [Read the guidance](https://github.com/pnp/powerplatform-samples/wiki/How-to-create-good-issues#mention-authors) and @mention the authors so they can respond to you." + only-issue-labels: "status:wrong-author" + close-issue-message: "Closing this issue due to lack of response. Feel free to open a new issue, but make sure to follow the guidance on [how to create good issues](https://github.com/pnp/powerplatform-samples/wiki/How-to-create-good-issues#mention-authors) and @mention the authors so they can respond to you." + - uses: actions/stale@v4 + name: "Close stale issues" + with: + days-before-issue-stale: 90 + days-before-issue-close: 7 + days-before-pr-stale: -1 + stale-issue-label: "status:no-recent-activity" + exempt-all-issue-assignees: true + exempt-issue-labels: "type:sample-request" + remove-issue-stale-when-updated: true + operations-per-run: 1000 + stale-issue-message: "This issue has been marked as stale due to no progress in over 90 days. If you are still experiencing this issue, please provide additional information so we can help you resolve it." + close-issue-message: "Closing this issue due to lack of activity. If you are still encountering this issue, please do not hesitate to open a new issue. Make sure to follow the guidance on [how to create good issues](https://github.com/pnp/powerplatform-samples/wiki/How-to-create-good-issues) to increase your chances of getting the help you deserve." diff --git a/.github/workflows/label-actions.yml b/.github/workflows/label-actions.yml new file mode 100644 index 00000000..3a956daa --- /dev/null +++ b/.github/workflows/label-actions.yml @@ -0,0 +1,14 @@ +name: 'Check for incomplete submissions' + +on: + issues: + types: [labeled, unlabeled] + +jobs: + reaction: + runs-on: ubuntu-latest + steps: + - uses: dessant/label-actions@v2 + with: + github-token: ${{ github.token }} + process-only: 'issues' diff --git a/.github/workflows/merge-sample-json.yml b/.github/workflows/merge-sample-json.yml new file mode 100644 index 00000000..947221d1 --- /dev/null +++ b/.github/workflows/merge-sample-json.yml @@ -0,0 +1,59 @@ +name: Merge sample metadata + +on: + push: + branches: + # When someone push to `main` branch + - main + paths: + - 'samples/**/assets/sample.json' + +jobs: + build: + name: 'Merge all sample.json files to samples.json' + runs-on: ubuntu-latest + steps: + - name: Checkout main branch + uses: actions/checkout@v2 + with: + ref: main + path: main + - name: Checkout gh-pages branch + uses: actions/checkout@v2 + with: + ref: gh-pages + path: gh-pages + - name: Checkout Docs branch + uses: actions/checkout@v2 + with: + ref: Docs + path: Docs + - name: Join samples + run: | + jq -s '[.[][]]' ./main/samples/**/assets/sample.json > ./Docs/docs/samples.json + - name: Validate JSON + uses: docker://orrosenblatt/validate-json-action:latest + env: + INPUT_SCHEMA: ./main/templates/metadata-schema.json + INPUT_JSONS: ./Docs/docs/samples.json + - name: copy file to gh-pages + uses: canastro/copy-file-action@master + with: + source: "./Docs/docs/samples.json" + target: "./gh-pages/samples.json" + - name: Commit samples.json to gh-pages + uses: EndBug/add-and-commit@v6 + with: + cwd: ./gh-pages + branch: gh-pages + add: 'samples.json --force' + push: true + token: ${{ secrets.GITHUB_TOKEN }} + - name: Commit samples.json to Docs + uses: EndBug/add-and-commit@v6 + with: + cwd: ./Docs + branch: Docs + add: 'docs/samples.json --force' + push: true + token: ${{ secrets.GITHUB_TOKEN }} diff --git a/.vscode/settings.json b/.vscode/settings.json new file mode 100644 index 00000000..5503c6e2 --- /dev/null +++ b/.vscode/settings.json @@ -0,0 +1,7 @@ +{ + "cSpell.words": [ + "CUSTOMCONNECTOR", + "ONPREM", + "POWERAPPS" + ] +} \ No newline at end of file diff --git a/.github/contributing.md b/CONTRIBUTING.md similarity index 70% rename from .github/contributing.md rename to CONTRIBUTING.md index 1c439706..a4e43cbf 100644 --- a/.github/contributing.md +++ b/CONTRIBUTING.md @@ -13,18 +13,16 @@ Remember that this repository is maintained by community members who volunteer t 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 how to use Power Platform or any of the provided samples, please use the following locations. +If you have questions about how to use Power Platform or any of the provided samples, please visit the [Power Platform Community](https://powerusers.microsoft.com/) at -* [Power Apps & Power Automate Community](https://techcommunity.microsoft.com/t5/power-apps-power-automate/bd-p/PowerAppFlow) at http://techcommunity.microsoft.com -* [Microsoft 365 PnP Community](https://techcommunity.microsoft.com/t5/microsoft-365-pnp/bd-p/Microsoft365PnP) for questions including Power Platform solutions ## Typos, Issues, Bugs and contributions -Whenever you are submitting any changes to the SharePoint repositories, please follow these recommendations. +Whenever you are submitting any changes to the community sample repositories, please follow these recommendations. * Always fork the repository to your own account before making your modifications * Do not combine multiple changes to one pull request. For example, submit any samples and documentation updates using separate PRs -* If your pull request shows merge conflicts, make sure to update your local master to be a mirror of what's in the main repo before making your modifications +* If your pull request shows merge conflicts, make sure to update your local main to be a mirror of what's in the main repo before making your modifications * If you are submitting multiple samples, please create a specific PR for each of them * If you are submitting typo or documentation fix, you can combine modifications to single PR where suitable @@ -32,19 +30,16 @@ Whenever you are submitting any changes to the SharePoint repositories, please f When you are submitting a new sample, it has to follow up below guidelines -* You will need to have a `README.md` file for your contribution, which is based on [the provided template](../samples/README-template.md) under the `samples` folder. Please copy this template to your project and update it accordingly. Your `README.md` must be named exactly `README.md` -- with capital letters -- as this is the information we use to make your sample public. +* You will need to have a `README.md` file for your contribution, which is based on [the provided template](templates\sample-template\README.md) under the `samples` folder. Please copy this template to your project and update it accordingly. Your `README.md` must be named exactly `README.md` -- with capital letters -- as this is the information we use to make your sample public. * You will need to have a screenshot picture of your sample in action in the `README.md` file ("pics or it didn't happen"). The preview image must be located in the `/assets/` folder in the root your you solution. -* The `README` template contains a specific tracking image at the bottom of the file with an `img` tag, where the `src` attribute points to `https://telemetry.sharepointpnp.com/powerplatform-samples/samples/readme-template`. This is a transparent image which is used to track viewership of individual samples in GitHub. - * Update the image `src` attribute according with the repository name and folder information. For example, if your sample is named `react-todo` in the `samples` folder, you should update the `src` attribute to `https://telemetry.sharepointpnp.com/powerplatform-samples/samples/react-todo` +* The `README` template contains a specific tracking image at the bottom of the file with an `img` tag, where the `src` attribute points to our telemetry tracker. This is a transparent image which is used to track viewership of individual samples in GitHub. + * Update the image `src` attribute according with the repository name and folder information. For example, if your sample is named `YOUR-SOLUTION-NAME` in the `samples` folder, you should update the `src` attribute to `https://m365-visitor-stats.azurewebsites.net/powerplatform-samples/samples/YOUR-SOLUTION-NAME` * If you find an existing sample which is similar to yours, please extend the existing one rather than submitting a new similar sample - * For example, if you use Office Graph with React, please add a new web part to the existing solution, rather than introducing a completely new solution + * For example, if you have an new Power Fx sample, please add a page to the existing solution, rather than introducing a completely new solution * When you update existing samples, please update also `README.md` file accordingly with information on provided changes and with your author details * When submitting a new sample solution, please name the sample solution folder accordingly - * Folder should start by identifying which product you used like `powerapps-`, `powerautomate-`, `portals-` - * If you are not using any specific product, but a combination of them, please use `powerplatform-` as the prefix for your sample - * Do not use words such as `sample`, `webpart` or `wp` in the folder or sample name - * If your solution is demonstrating multiple technologies, please use functional terms as the name for the solution folder * Do not use period/dot in the folder name of the provided sample +* All folders should be in lower case ## Submitting Pull Requests @@ -52,13 +47,13 @@ Here's a high-level process for submitting new samples or updates to existing on 1. Sign the Contributor License Agreement (see below) 2. Fork this repository [pnp/powerplatform-samples](https://github.com/pnp/powerplatform-samples) to your GitHub account -3. Create a new branch from the `master` branch for your fork for the contribution +3. Create a new branch from the `main` branch for your fork for the contribution 4. Include your changes to your branch 5. Commit your changes using descriptive commit message * These are used to track changes on the repositories for monthly communications -6. Create a pull request in your own fork and target the `master` branch +6. Create a pull request in your own fork and target the `main` branch 7. Fill up the provided PR template with the requested details -If you feel insecure about that process or are new to GitHub, please consider to attend the [Sharing Is Caring sessions from the PnP team](https://pnp.github.io/sharing-is-caring/#pnp-sic-events) in which the Microsoft 365 PnP team provides hands-on guidance for first time contributors. +If you feel insecure about that process or are new to GitHub, please consider to attend the [Sharing Is Caring sessions from the PnP team](https://pnp.github.io/sharing-is-caring/#pnp-sic-events) in which the Microsoft 365 PnP team provides hands-on guidance for first time contributors. Before you submit your pull request consider the following guidelines: @@ -79,7 +74,7 @@ Before you submit your pull request consider the following guidelines: * Make your changes in a new git branch: ```shell - git checkout -b react-taxonomypicker master + git checkout -b YOUR-SOLUTION-NAME main ``` * Ensure your fork is updated and not behind the upstream **powerplatform-samples** repo. Refer to these resources for more information on syncing your repo: @@ -89,25 +84,25 @@ Before you submit your pull request consider the following guidelines: ```shell # assuming you are in the folder of your locally cloned fork.... - git checkout master + git checkout main # assuming you have a remote named `upstream` pointing official **powerplatform-samples** repo git fetch upstream - # update your local master to be a mirror of what's in the main repo - git pull --rebase upstream master + # update your local main to be a mirror of what's in the main repo + git pull --rebase upstream main - # switch to your branch where you are working, say "react-taxonomypicker" - git checkout react-taxonomypicker + # switch to your branch where you are working, say "YOUR-SOLUTION-NAME" + git checkout YOUR-SOLUTION-NAME - # update your branch to update it's fork point to the current tip of master & put your changes on top of it - git rebase master + # update your branch to update it's fork point to the current tip of main & put your changes on top of it + git rebase main ``` * Push your branch to GitHub: ```shell - git push origin react-taxonomypicker + git push origin YOUR-SOLUTION-NAME ``` ## Merging your Existing GitHub Projects with this Repository @@ -127,26 +122,26 @@ If the sample you wish to contribute is stored in your own GitHub repository, yo ```shell git remote add origin https://github.com/yourgitaccount/powerplatform-samples.git - git pull origin master + git pull origin main ``` * Pull your other project from GitHub into the `samples` folder of your local copy of `powerplatform-samples` ```shell - git subtree add --prefix=samples/projectname https://github.com/yourgitaccount/projectname.git master + git subtree add --prefix=samples/YOUR-SOLUTION-NAME https://github.com/yourgitaccount/YOUR-SOLUTION-NAME.git main ``` * Push the changes up to your forked repository ```shell - git push origin master + git push origin main ``` ## Signing the CLA Before we can accept your pull requests you will be asked to sign electronically Contributor License Agreement (CLA), which is a pre-requisite for any contributions all PnP repositories. 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 at your submission for a 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. +You can find Microsoft CLA from the following address - . Thank you for your contribution. diff --git a/README.md b/README.md index bc7d1905..d914fbde 100644 --- a/README.md +++ b/README.md @@ -11,6 +11,8 @@ We are currently in the process of moving all the per product samples into solut - [Power Automate Samples](https://github.com/pnp/powerautomate-samples) - [Power Virtual Agents Samples](https://github.com/pnp/powerva-samples) +> You're welcome to bring samples from the other repositories! The more people help, the faster we'll move all the samples here. + ## Have issues or questions? Please use following logic on submitting your questions or issues to right location to ensure that they are noticed and addressed as soon as possible. diff --git a/samples/chucknorrisio/assets/sample.json b/samples/chucknorrisio/assets/sample.json index 2af62287..23ad6127 100644 --- a/samples/chucknorrisio/assets/sample.json +++ b/samples/chucknorrisio/assets/sample.json @@ -1,7 +1,7 @@ [ { "$schema": "https://developer.microsoft.com/en-us/json-schemas/pnp/samples/v1.0/metadata-schema.json", - "name": "pnp-powerplatform-samples-ChuckNorrisIO", + "name": "pnp-powerplatform-samples-chucknorrisio", "version": "1.0.0.0", "source": "pnp", "creationDateTime": "2023-03-16T00:00:00.000Z", @@ -11,7 +11,7 @@ "longDescription": [ "Power App that demonstrates the use of the Chuck Norris IO Independent Publisher connector." ], - "url": "https://github.com/pnp/powerplatform-samples/tree/main/samples/ChuckNorrisIO", + "url": "https://github.com/pnp/powerplatform-samples/tree/main/samples/chucknorrisio", "products": [ "Power Apps", "Power Platform" diff --git a/templates/metadata-schema.json b/templates/metadata-schema.json index ea08f4ed..96ca4cc5 100644 --- a/templates/metadata-schema.json +++ b/templates/metadata-schema.json @@ -7,7 +7,7 @@ "properties": { "name": { "type": "string", - "pattern": "pnp-sp-dev-spfx-web-parts-.*" + "pattern": "pnp-powerplatform-samples-.*" }, "version": { "type": "string" @@ -22,7 +22,7 @@ }, "url": { "type": "string", - "pattern": "https:\/\/github.com\/pnp\/sp-dev-fx-webparts\/tree\/main\/samples\/.*" + "pattern": "https:\/\/github.com\/pnp\/powerplatform-samples\/tree\/main\/samples\/.*" }, "creationDateTime": { "type": "string", diff --git a/templates/sample-template/README.md b/templates/sample-template/README.md index 57bfe746..e6c6277d 100644 --- a/templates/sample-template/README.md +++ b/templates/sample-template/README.md @@ -116,7 +116,7 @@ Version|Date|Comments ## Prerequisites