|
| 1 | +comment: |
| 2 | + # header: "Please note the following requirement:" |
| 3 | + footer: "\ |
| 4 | + ---\n\n |
| 5 | + > 	 	 	 	 Be sure to [join the community](https://slack.meshery.io), if you haven't yet and please leave a :star: [star on the project](../stargazers) :smile: |
| 6 | + " |
| 7 | + |
| 8 | +labels: |
| 9 | + - name: issue/design required |
| 10 | + labeled: |
| 11 | + issue: |
| 12 | + body: This issue has been labeled with 'design-required'. Note that prior to commencing on implementation, a design specification needs to be created and reviewed for approval. See [Creating a Functional Specification](https://docs.google.com/document/d/1RP3IWLc-MiQS-QYasqCoVuCH7--G87p5ezE5f_nOzB8/edit?usp=sharing) to create a design spec. |
| 13 | + action: open |
| 14 | + - name: issue/remind |
| 15 | + labeled: |
| 16 | + issue: |
| 17 | + body: Checking in... it has been awhile since we've heard from you on this issue. Are you still working on it? Please let us know and please don't hesitate to contact a [MeshMate](https://layer5.io/community/meshmates/) or any other [community member](https://layer5.io/community/members) for assistance. |
| 18 | + action: open |
| 19 | + pr: |
| 20 | + body: Checking in... it has been awhile since we've heard from you on this issue. Are you still working on it? Please let us know and please don't hesitate to contact a [MeshMate](https://layer5.io/community/meshmates/) or any other [community member](https://layer5.io/community/members) for assistance. |
| 21 | + action: open |
| 22 | + - name: issue/dco |
| 23 | + labeled: |
| 24 | + issue: |
| 25 | + body: "🚨 Alert! Git Police! We couldn’t help but notice that one or more of your commits is missing a sign-off. _A what?_ A commit sign-off (your email address).\n\n |
| 26 | + To amend the commits in this PR with your signoff using the instructions provided in the DCO check. \n\n |
| 27 | + To configure your dev environment to automatically signoff on your commits in the future, see [these instructions](https://github.com/meshery/meshery/blob/master/CONTRIBUTING.md#signing-off-on-commits-developer-certificate-of-origin)." |
| 28 | + action: open |
| 29 | + pr: |
| 30 | + body: "🚨 Alert! Git Police! We couldn’t help but notice that one or more of your commits is missing a sign-off. _A what?_ A commit sign-off (your email address).\n\n |
| 31 | + To amend the commits in this PR with your signoff using the instructions provided in the DCO check. \n\n |
| 32 | + To configure your dev environment to automatically signoff on your commits in the future, see [these instructions](https://github.com/meshery/meshery/blob/master/CONTRIBUTING.md#signing-off-on-commits-developer-certificate-of-origin)." |
| 33 | + action: open |
| 34 | + - name: component/ui |
| 35 | + labeled: |
| 36 | + issue: |
| 37 | + body: This issue has been labeled with 'component/ui'. 🧰 Here are docs on [Contributing to Meshery UI](https://docs.meshery.io/project/contributing/contributing-ui). 🎨 Here is the [Meshery UI Figma File](https://www.figma.com/file/SMP3zxOjZztdOLtgN4dS2W/Meshery-UI?node-id=4%3A0) File. Lastly, here are docs on [Contributing to Meshery's End-to-End Tests Using Cypress](https://docs.meshery.io/project/contributing/contributing-cypress). |
| 38 | + action: open |
| 39 | + pr: |
| 40 | + body: This PR has been labeled with 'component/ui'. 🧰 Here are docs on [Contributing to Meshery UI](https://docs.meshery.io/project/contributing/contributing-ui). 🎨 Here is the [Meshery UI Figma File](https://www.figma.com/file/SMP3zxOjZztdOLtgN4dS2W/Meshery-UI?node-id=4%3A0) File. Lastly, here are docs on [Contributing to Meshery's End-to-End Tests Using Cypress](https://docs.meshery.io/project/contributing/contributing-cypress) |
| 41 | + action: open |
| 42 | + - name: component/mesheryctl |
| 43 | + labeled: |
| 44 | + issue: |
| 45 | + body: This issue has been labeled with 'component/mesheryctl'. Note that after making changes you need to update it in the [mesheryctl command tracker](https://docs.google.com/spreadsheets/d/1q63sIGAuCnIeDs8PeM-0BAkNj8BBgPUXhLbe1Y-318o/edit#gid=0) spreadsheet. |
| 46 | + action: open |
| 47 | + pr: |
| 48 | + body: This PR has been labeled with 'component/mesheryctl'. Note that after making changes you need to update it in the [mesheryctl command tracker](https://docs.google.com/spreadsheets/d/1q63sIGAuCnIeDs8PeM-0BAkNj8BBgPUXhLbe1Y-318o/edit#gid=0) spreadsheet. |
| 49 | + action: open |
| 50 | + # pr: |
| 51 | + # body: Hi, please note that this issue will need an approved design specification before implementation proceeds. See [Creating a Functional Specification](https://docs.google.com/document/d/1RP3IWLc-MiQS-QYasqCoVuCH7--G87p5ezE5f_nOzB8/edit?usp=sharing) to create a design spec. |
| 52 | + # action: open |
0 commit comments