Skip to content

Commit 22b4a03

Browse files
jeromelabanjeromelaban
committed
Initial commit
0 parents  commit 22b4a03

24 files changed

+1174
-0
lines changed

‎.dependabot/config.yml

+9
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,9 @@
1+
version: 1
2+
update_configs:
3+
- package_manager: "dotnet:nuget"
4+
directory: "/"
5+
update_schedule: "weekly"
6+
7+
default_labels:
8+
- "kind/dependency"
9+
- "do-not-merge/work-in-progress"

‎.github/CODEOWNERS

+6
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,6 @@
1+
# A CODEOWNERS file uses a pattern that follows the same rules used in gitignore files.
2+
# The pattern is followed by one or more GitHub usernames or team names using the
3+
# standard @username or @org/team-name format. You can also refer to a user by an
4+
# email address that has been added to their GitHub account, for example [email protected]
5+
6+
* @unoplatform/maintainers

‎.github/ISSUE_TEMPLATE/bug-report.md

+53
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,53 @@
1+
---
2+
name: Bug Report
3+
about: Report a bug encountered while developing with Uno
4+
labels: kind/bug, triage/untriaged
5+
---
6+
7+
<!-- Please use this template while reporting a bug and provide as much info as possible. Not doing so may result in your bug not being addressed in a timely manner. Thanks!
8+
9+
If the matter is security related, please disclose it privately via https://github.com/nventive/Uno/security/
10+
-->
11+
12+
## Current behavior
13+
14+
<!-- Describe how the issue manifests. -->
15+
16+
## Expected behavior
17+
18+
<!-- Describe what the desired behavior would be. -->
19+
20+
## How to reproduce it (as minimally and precisely as possible)
21+
22+
<!-- Please provide a **MINIMAL REPRO PROJECT** and the **STEPS TO REPRODUCE**-->
23+
24+
## Environment
25+
26+
<!-- For bug reports Check one or more of the following options with "x" -->
27+
28+
Nuget Package:
29+
30+
Package Version(s):
31+
32+
Affected platform(s):
33+
34+
- [ ] iOS
35+
- [ ] Android
36+
- [ ] WebAssembly
37+
- [ ] WebAssembly renders for Xamarin.Forms
38+
- [ ] Windows
39+
- [ ] Build tasks
40+
41+
Visual Studio:
42+
43+
- [ ] 2017 (version: )
44+
- [ ] 2019 (version: )
45+
- [ ] for Mac (version: )
46+
47+
Relevant plugins:
48+
49+
- [ ] Resharper (version: )
50+
51+
## Anything else we need to know?
52+
53+
<!-- We would love to know of any friction, apart from knowledge, that prevented you from sending in a pull-request -->

‎.github/ISSUE_TEMPLATE/documentation-issue.md

+17
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
name: Documentation Issue
3+
about: Report an issue with the Uno documentation
4+
labels: kind/consumer-experience, kind/documentation, triage/untriaged
5+
---
6+
7+
<!-- Please only use this template for reporting issues with the documentation where the fix isn't clear. We greatly appreciate it when people send in pull-requests with fixes. If there's any friction, apart from knowledge, that's preventing you from doing so please let us know below. -->
8+
9+
## On which page?
10+
11+
## What's wrong?
12+
13+
## Any feedback?
14+
15+
16+
17+

‎.github/ISSUE_TEMPLATE/documentation-request.md

+32
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
---
2+
name: Documentation Request
3+
about: Request an enhancement to the Uno documentation
4+
labels: kind/consumer-experience, kind/documentation, triage/untriaged
5+
---
6+
7+
<!-- Please only use this template for submitting documentation requests -->
8+
9+
## What would you like clarification on:
10+
11+
## Concern?
12+
13+
- [ ] Usage in industry
14+
- [ ] Clarification of capabilities
15+
- [ ] Getting started with Uno
16+
- [ ] Developing with Uno
17+
- [ ] Contributing to the Uno project
18+
- [ ] Publishing your application
19+
- [ ] Support
20+
- [ ] Other (please specify):
21+
22+
## For which Platform:
23+
24+
- [ ] iOS
25+
- [ ] Android
26+
- [ ] WebAssembly
27+
- [ ] Windows
28+
29+
## Anything else we need to know?
30+
31+
<!-- We would love to know of any friction, apart from knowledge, that prevented you from sending in a pull-request -->
32+

‎.github/ISSUE_TEMPLATE/enhancement.md

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
name: Enhancement Request
3+
about: Suggest an enhancement to the Uno project
4+
labels: kind/enhancement, triage/untriaged
5+
---
6+
7+
<!-- Please only use this template for submitting enhancement requests -->
8+
9+
## What would you like to be added:
10+
11+
## Why is this needed:
12+
13+
## For which Platform:
14+
15+
- [ ] iOS
16+
- [ ] Android
17+
- [ ] WebAssembly
18+
- [ ] WebAssembly renders for Xamarin.Forms
19+
- [ ] Windows
20+
- [ ] Build tasks
21+
22+
## Anything else we need to know?
23+

‎.github/ISSUE_TEMPLATE/feedback.md

+22
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
---
2+
name: Feedback
3+
about: Share feedback with the Uno team 💖
4+
labels: kind/feedback, triage/untriaged
5+
---
6+
7+
<!-- Thanks for stopping on by to share feedback 💖
8+
9+
If you are after inspiration, folks typically submit feedback on the following topics:
10+
11+
- what version of Uno and what platforms you are using it with?
12+
- what do you like?
13+
- what is lacking?
14+
- what do you long for going forward?
15+
- where and how you have used Uno in production?
16+
- any friction that hinders adoption of Uno at your company.
17+
- any friction that's preventing you from contributing to Uno.
18+
19+
If you are representing an organization that wishes to discuss in private, please [contact us](https://platform.uno/contact/).
20+
21+
-->
22+

‎.github/ISSUE_TEMPLATE/samples-issue.md

+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
name: Samples Issue
3+
about: Report an issue with the Uno samples
4+
labels: kind/contributor-experience, kind/documentation, triage/untriaged
5+
---
6+
7+
<!-- Please only use this template for reporting issues with the samples where the fix isn't clear. We greatly appreciate it when people send in pull-requests with fixes. If there's any friction, apart from knowledge, that's preventing you from doing so please let us know below. -->
8+
9+
## On which page?
10+
11+
## What's wrong?
12+
13+
## Any feedback?
14+

‎.github/ISSUE_TEMPLATE/samples-request.md

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
---
2+
name: Samples Request
3+
about: Request an enhancement to the Uno samples
4+
labels: kind/contributor-experience, kind/documentation, triage/untriaged
5+
---
6+
7+
<!-- Please only use this template for submitting enhancement requests -->
8+
9+
## What would you like to be added:
10+
11+
## Why is this needed:
12+
13+
## For which Platform:
14+
15+
- [ ] iOS
16+
- [ ] Android
17+
- [ ] WebAssembly
18+
- [ ] WebAssembly Renderers for Xamarin.Forms
19+
- [ ] Windows
20+
21+
## Anything else we need to know?
22+
23+
<!-- We would love to know of any friction, apart from knowledge, that prevented you from sending in a pull-request -->

‎.github/ISSUE_TEMPLATE/success-story.md

+16
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,16 @@
1+
---
2+
name: Success Story
3+
about: If you are using Uno in production, we would love to hear about it.
4+
labels: kind/consumer-experience, kind/documentation, triage/untriaged
5+
---
6+
7+
<!-- STOP -- PLEASE READ!
8+
9+
We 💖 to hear about how, where and what you're doing with Uno. Sharing this information is one of the kindest things you can do in open-source and the maintainers love hearing about success stories. Instead of raising a new GitHub issue could you please comment in the existing thread?
10+
11+
https://github.com/nventive/Uno/issues/18#issuecomment-494887105
12+
13+
If you are feeling extra generous, how about authoring up a blog post and then letting us know about it so that we can retweet it?
14+
15+
Thank-you!
16+

‎.github/ISSUE_TEMPLATE/support.md

+17
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
name: Support Request
3+
about: Support request or question relating to Uno
4+
labels: triage/support
5+
---
6+
7+
<!-- STOP -- PLEASE READ!
8+
9+
GitHub is not the right place for support requests.
10+
11+
If you're looking for help, check [Stack Overflow](https://stackoverflow.com/questions/tagged/uno-platform) and the [documentation](https://platform.uno/docs/).
12+
13+
You can also post your question in the [Uno gitter room](https://gitter.im/uno-platform/Lobby) or [on Twitter using the #unoplatform](https://twitter.com/search?q=%23unoplatform) hashtag.
14+
15+
For organizations that want a deeper level of support beyond our community support, please [contact us](https://platform.uno/contact/). Our professional support is more than a contract – it is a shared responsibility for your project success. Our engineering team will collaborate with you to ensure the success of your projects, and our custom application development team at nventive is also available to lend its expertise.
16+
17+
If the matter is security related, please disclose it privately via https://github.com/nventive/Uno/security/ -->

‎.github/config.yml

+23
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# Configuration for welcome - https://github.com/behaviorbot/welcome
2+
3+
## Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
4+
5+
# Comment to be posted to on first time issues
6+
#newIssueWelcomeComment: >
7+
# Thanks for opening your first issue here! Be sure to follow the issue template!
8+
9+
## Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
10+
11+
# Comment to be posted to on PRs from first time contributors in your repository
12+
#newPRWelcomeComment: >
13+
# Thanks for opening this pull request! Please check out our contributing guidelines.
14+
15+
## Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
16+
17+
# Comment to be posted to on pull requests merged by a first time user
18+
firstPRMergeComment: >
19+
Congrats on your first pull-request! We ❤ the people who are involved in this project, and we’d love to pay it forward by [sending you some swag](https://forms.office.com/Pages/ResponsePage.aspx?id=Ye9TbdG2UEGuC0O5DnXgzcxnnVo6zspHjmNPgM3UO41UNFpFU01TV1UxU0FWRTNMNFJUTlBLMjhIWi4u). If you have any feedback (or ideas how to improve Uno as a open-source project) please [open a feedback issue](https://github.com/unoplatform/uno/issues/new?labels=kind%2Ffeedback%2C+triage%2Funtriaged&template=feedback.md).
20+
<br>
21+
![giphy](https://user-images.githubusercontent.com/127353/66220548-37ae4d00-e69b-11e9-8a16-f08f87b3b27c.gif)
22+
<br>
23+
Merci beaucoup 👋

‎.github/invite-contributors.yml

+3
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,3 @@
1+
# automatically invite contributors to this particular team in the organization when their pull-requests
2+
# are merged which enables maintainers to assign issues to these individuals.
3+
team: community

‎.github/no-response.yml

+11
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,11 @@
1+
# Configuration for probot-no-response - https://github.com/probot/no-response
2+
3+
# Number of days of inactivity before an Issue is closed for lack of response
4+
daysUntilClose: 20
5+
6+
# Label requiring a response
7+
responseRequiredLabel: triage/needs-information
8+
9+
# Comment to post when closing an Issue for lack of response. Set to `false` to disable
10+
closeComment: >
11+
This issue has been automatically closed because there has been no response to our request for more information from the original author. With only the information that is currently in the issue, we don't have enough information to take action. We don't monitor discussions on closed issues thus please open a new GitHub issue if you need the team to revisit this matter.

‎.github/pull_request_template.md

+52
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,52 @@
1+
GitHub Issue (If applicable): #
2+
3+
<!-- Link to relevant GitHub issue if applicable. All PRs should be associated with an issue (GitHub issue or internal) -->
4+
5+
## PR Type
6+
7+
What kind of change does this PR introduce?
8+
<!-- Please uncomment one ore more that apply to this PR
9+
10+
- Bugfix
11+
- Feature
12+
- Code style update (formatting)
13+
- Refactoring (no functional changes, no api changes)
14+
- Build or CI related changes
15+
- Documentation content changes
16+
- Project automation
17+
- Other... Please describe:
18+
19+
-->
20+
21+
## What is the current behavior?
22+
23+
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
24+
25+
26+
## What is the new behavior?
27+
28+
<!-- Please describe the new behavior after your modifications. -->
29+
30+
31+
## PR Checklist
32+
33+
Please check if your PR fulfills the following requirements:
34+
35+
- [ ] Tested code with current [supported SDKs](../README.md#supported)
36+
- [ ] Docs have been added/updated which fit [documentation template](https://github.com/nventive/Uno/blob/master/doc/.feature-template.md). (for bug fixes / features)
37+
- [ ] [Unit Tests and/or UI Tests](doc/articles/working-with-the-samples-apps.md) for the changes have been added (for bug fixes / features) (if applicable)
38+
- [ ] [Wasm UI Tests](doc/articles/working-with-the-samples-apps.md#running-the-webassembly-ui-tests-snapshots) are not showing unexpected any differences. Validate PR `Screenshots Compare Test Run` results.
39+
- [ ] Contains **NO** breaking changes
40+
- [ ] Updated the [Release Notes](https://github.com/nventive/Uno/tree/master/doc/ReleaseNotes)
41+
- [ ] Associated with an issue (GitHub or internal)
42+
43+
<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below.
44+
Please note that breaking changes are likely to be rejected -->
45+
46+
47+
## Other information
48+
49+
<!-- Please provide any additional information if necessary -->
50+
51+
Internal Issue (If applicable):
52+
<!-- Link to relevant internal issue if applicable. All PRs should be associated with an issue (GitHub issue or internal) -->

0 commit comments

Comments
 (0)