Initial commit
This commit is contained in:
Jérôme Laban
Коммит
01d2ea1ad2
|
|
@ -0,0 +1,9 @@
|
|||
version: 1
|
||||
update_configs:
|
||||
- package_manager: "dotnet:nuget"
|
||||
directory: "/"
|
||||
update_schedule: "weekly"
|
||||
|
||||
default_labels:
|
||||
- "kind/dependency"
|
||||
- "do-not-merge/work-in-progress"
|
||||
|
|
@ -0,0 +1,6 @@
|
|||
# A CODEOWNERS file uses a pattern that follows the same rules used in gitignore files.
|
||||
# The pattern is followed by one or more GitHub usernames or team names using the
|
||||
# standard @username or @org/team-name format. You can also refer to a user by an
|
||||
# email address that has been added to their GitHub account, for example user@example.com
|
||||
|
||||
* @unoplatform/maintainers
|
||||
|
|
@ -0,0 +1,53 @@
|
|||
---
|
||||
name: Bug Report
|
||||
about: Report a bug encountered while developing with Uno
|
||||
labels: kind/bug, triage/untriaged
|
||||
---
|
||||
|
||||
<!-- 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!
|
||||
|
||||
If the matter is security related, please disclose it privately via https://github.com/nventive/Uno/security/
|
||||
-->
|
||||
|
||||
## Current behavior
|
||||
|
||||
<!-- Describe how the issue manifests. -->
|
||||
|
||||
## Expected behavior
|
||||
|
||||
<!-- Describe what the desired behavior would be. -->
|
||||
|
||||
## How to reproduce it (as minimally and precisely as possible)
|
||||
|
||||
<!-- Please provide a **MINIMAL REPRO PROJECT** and the **STEPS TO REPRODUCE**-->
|
||||
|
||||
## Environment
|
||||
|
||||
<!-- For bug reports Check one or more of the following options with "x" -->
|
||||
|
||||
Nuget Package:
|
||||
|
||||
Package Version(s):
|
||||
|
||||
Affected platform(s):
|
||||
|
||||
- [ ] iOS
|
||||
- [ ] Android
|
||||
- [ ] WebAssembly
|
||||
- [ ] WebAssembly renders for Xamarin.Forms
|
||||
- [ ] Windows
|
||||
- [ ] Build tasks
|
||||
|
||||
Visual Studio:
|
||||
|
||||
- [ ] 2017 (version: )
|
||||
- [ ] 2019 (version: )
|
||||
- [ ] for Mac (version: )
|
||||
|
||||
Relevant plugins:
|
||||
|
||||
- [ ] Resharper (version: )
|
||||
|
||||
## Anything else we need to know?
|
||||
|
||||
<!-- We would love to know of any friction, apart from knowledge, that prevented you from sending in a pull-request -->
|
||||
|
|
@ -0,0 +1,17 @@
|
|||
---
|
||||
name: Documentation Issue
|
||||
about: Report an issue with the Uno documentation
|
||||
labels: kind/consumer-experience, kind/documentation, triage/untriaged
|
||||
---
|
||||
|
||||
<!-- 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. -->
|
||||
|
||||
## On which page?
|
||||
|
||||
## What's wrong?
|
||||
|
||||
## Any feedback?
|
||||
|
||||
|
||||
|
||||
|
||||
|
|
@ -0,0 +1,32 @@
|
|||
---
|
||||
name: Documentation Request
|
||||
about: Request an enhancement to the Uno documentation
|
||||
labels: kind/consumer-experience, kind/documentation, triage/untriaged
|
||||
---
|
||||
|
||||
<!-- Please only use this template for submitting documentation requests -->
|
||||
|
||||
## What would you like clarification on:
|
||||
|
||||
## Concern?
|
||||
|
||||
- [ ] Usage in industry
|
||||
- [ ] Clarification of capabilities
|
||||
- [ ] Getting started with Uno
|
||||
- [ ] Developing with Uno
|
||||
- [ ] Contributing to the Uno project
|
||||
- [ ] Publishing your application
|
||||
- [ ] Support
|
||||
- [ ] Other (please specify):
|
||||
|
||||
## For which Platform:
|
||||
|
||||
- [ ] iOS
|
||||
- [ ] Android
|
||||
- [ ] WebAssembly
|
||||
- [ ] Windows
|
||||
|
||||
## Anything else we need to know?
|
||||
|
||||
<!-- We would love to know of any friction, apart from knowledge, that prevented you from sending in a pull-request -->
|
||||
|
||||
|
|
@ -0,0 +1,23 @@
|
|||
---
|
||||
name: Enhancement Request
|
||||
about: Suggest an enhancement to the Uno project
|
||||
labels: kind/enhancement, triage/untriaged
|
||||
---
|
||||
|
||||
<!-- Please only use this template for submitting enhancement requests -->
|
||||
|
||||
## What would you like to be added:
|
||||
|
||||
## Why is this needed:
|
||||
|
||||
## For which Platform:
|
||||
|
||||
- [ ] iOS
|
||||
- [ ] Android
|
||||
- [ ] WebAssembly
|
||||
- [ ] WebAssembly renders for Xamarin.Forms
|
||||
- [ ] Windows
|
||||
- [ ] Build tasks
|
||||
|
||||
## Anything else we need to know?
|
||||
|
||||
|
|
@ -0,0 +1,22 @@
|
|||
---
|
||||
name: Feedback
|
||||
about: Share feedback with the Uno team 💖
|
||||
labels: kind/feedback, triage/untriaged
|
||||
---
|
||||
|
||||
<!-- Thanks for stopping on by to share feedback 💖
|
||||
|
||||
If you are after inspiration, folks typically submit feedback on the following topics:
|
||||
|
||||
- what version of Uno and what platforms you are using it with?
|
||||
- what do you like?
|
||||
- what is lacking?
|
||||
- what do you long for going forward?
|
||||
- where and how you have used Uno in production?
|
||||
- any friction that hinders adoption of Uno at your company.
|
||||
- any friction that's preventing you from contributing to Uno.
|
||||
|
||||
If you are representing an organization that wishes to discuss in private, please [contact us](https://platform.uno/contact/).
|
||||
|
||||
-->
|
||||
|
||||
|
|
@ -0,0 +1,14 @@
|
|||
---
|
||||
name: Samples Issue
|
||||
about: Report an issue with the Uno samples
|
||||
labels: kind/contributor-experience, kind/documentation, triage/untriaged
|
||||
---
|
||||
|
||||
<!-- 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. -->
|
||||
|
||||
## On which page?
|
||||
|
||||
## What's wrong?
|
||||
|
||||
## Any feedback?
|
||||
|
||||
|
|
@ -0,0 +1,23 @@
|
|||
---
|
||||
name: Samples Request
|
||||
about: Request an enhancement to the Uno samples
|
||||
labels: kind/contributor-experience, kind/documentation, triage/untriaged
|
||||
---
|
||||
|
||||
<!-- Please only use this template for submitting enhancement requests -->
|
||||
|
||||
## What would you like to be added:
|
||||
|
||||
## Why is this needed:
|
||||
|
||||
## For which Platform:
|
||||
|
||||
- [ ] iOS
|
||||
- [ ] Android
|
||||
- [ ] WebAssembly
|
||||
- [ ] WebAssembly Renderers for Xamarin.Forms
|
||||
- [ ] Windows
|
||||
|
||||
## Anything else we need to know?
|
||||
|
||||
<!-- We would love to know of any friction, apart from knowledge, that prevented you from sending in a pull-request -->
|
||||
|
|
@ -0,0 +1,16 @@
|
|||
---
|
||||
name: Success Story
|
||||
about: If you are using Uno in production, we would love to hear about it.
|
||||
labels: kind/consumer-experience, kind/documentation, triage/untriaged
|
||||
---
|
||||
|
||||
<!-- STOP -- PLEASE READ!
|
||||
|
||||
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?
|
||||
|
||||
https://github.com/nventive/Uno/issues/18#issuecomment-494887105
|
||||
|
||||
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?
|
||||
|
||||
Thank-you!
|
||||
|
||||
|
|
@ -0,0 +1,17 @@
|
|||
---
|
||||
name: Support Request
|
||||
about: Support request or question relating to Uno
|
||||
labels: triage/support
|
||||
---
|
||||
|
||||
<!-- STOP -- PLEASE READ!
|
||||
|
||||
GitHub is not the right place for support requests.
|
||||
|
||||
If you're looking for help, check [Stack Overflow](https://stackoverflow.com/questions/tagged/uno-platform) and the [documentation](https://platform.uno/docs/).
|
||||
|
||||
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.
|
||||
|
||||
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.
|
||||
|
||||
If the matter is security related, please disclose it privately via https://github.com/nventive/Uno/security/ -->
|
||||
|
|
@ -0,0 +1,23 @@
|
|||
# Configuration for welcome - https://github.com/behaviorbot/welcome
|
||||
|
||||
## Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
|
||||
|
||||
# Comment to be posted to on first time issues
|
||||
#newIssueWelcomeComment: >
|
||||
# Thanks for opening your first issue here! Be sure to follow the issue template!
|
||||
|
||||
## Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
|
||||
|
||||
# Comment to be posted to on PRs from first time contributors in your repository
|
||||
#newPRWelcomeComment: >
|
||||
# Thanks for opening this pull request! Please check out our contributing guidelines.
|
||||
|
||||
## Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
|
||||
|
||||
# Comment to be posted to on pull requests merged by a first time user
|
||||
firstPRMergeComment: >
|
||||
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=Ye9TbdG2UEGuC0O5DnXgzai0HkTgxONNjPmzuZ5zgdRUQzFJMVBPSU8xWDBUUlNOTExCWFUwQjNBNy4u). 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).
|
||||
<br>
|
||||
|
||||
<br>
|
||||
Merci beaucoup 👋
|
||||
|
|
@ -0,0 +1,3 @@
|
|||
# automatically invite contributors to this particular team in the organization when their pull-requests
|
||||
# are merged which enables maintainers to assign issues to these individuals.
|
||||
team: community
|
||||
|
|
@ -0,0 +1,11 @@
|
|||
# Configuration for probot-no-response - https://github.com/probot/no-response
|
||||
|
||||
# Number of days of inactivity before an Issue is closed for lack of response
|
||||
daysUntilClose: 20
|
||||
|
||||
# Label requiring a response
|
||||
responseRequiredLabel: triage/needs-information
|
||||
|
||||
# Comment to post when closing an Issue for lack of response. Set to `false` to disable
|
||||
closeComment: >
|
||||
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.
|
||||
|
|
@ -0,0 +1,52 @@
|
|||
GitHub Issue (If applicable): #
|
||||
|
||||
<!-- Link to relevant GitHub issue if applicable. All PRs should be associated with an issue (GitHub issue or internal) -->
|
||||
|
||||
## PR Type
|
||||
|
||||
What kind of change does this PR introduce?
|
||||
<!-- Please uncomment one ore more that apply to this PR
|
||||
|
||||
- Bugfix
|
||||
- Feature
|
||||
- Code style update (formatting)
|
||||
- Refactoring (no functional changes, no api changes)
|
||||
- Build or CI related changes
|
||||
- Documentation content changes
|
||||
- Project automation
|
||||
- Other... Please describe:
|
||||
|
||||
-->
|
||||
|
||||
## What is the current behavior?
|
||||
|
||||
<!-- Please describe the current behavior that you are modifying, or link to a relevant issue. -->
|
||||
|
||||
|
||||
## What is the new behavior?
|
||||
|
||||
<!-- Please describe the new behavior after your modifications. -->
|
||||
|
||||
|
||||
## PR Checklist
|
||||
|
||||
Please check if your PR fulfills the following requirements:
|
||||
|
||||
- [ ] Tested code with current [supported SDKs](../README.md#supported)
|
||||
- [ ] Docs have been added/updated which fit [documentation template](https://github.com/nventive/Uno/blob/master/doc/.feature-template.md). (for bug fixes / features)
|
||||
- [ ] [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)
|
||||
- [ ] [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.
|
||||
- [ ] Contains **NO** breaking changes
|
||||
- [ ] Updated the [Release Notes](https://github.com/nventive/Uno/tree/master/doc/ReleaseNotes)
|
||||
- [ ] Associated with an issue (GitHub or internal)
|
||||
|
||||
<!-- If this PR contains a breaking change, please describe the impact and migration path for existing applications below.
|
||||
Please note that breaking changes are likely to be rejected -->
|
||||
|
||||
|
||||
## Other information
|
||||
|
||||
<!-- Please provide any additional information if necessary -->
|
||||
|
||||
Internal Issue (If applicable):
|
||||
<!-- Link to relevant internal issue if applicable. All PRs should be associated with an issue (GitHub issue or internal) -->
|
||||
|
|
@ -0,0 +1,208 @@
|
|||
# These settings are synced to GitHub by https://probot.github.io/apps/settings/
|
||||
|
||||
repository:
|
||||
# See https://developer.github.com/v3/repos/#edit for all available settings.
|
||||
|
||||
# The name of the repository. Changing this will rename the repository
|
||||
#name: template
|
||||
|
||||
description: template for brand new github repositories
|
||||
homepage: https://platform.uno/
|
||||
topics: uno, uno-platform, webassembly, wasm, uwp, mono, xamarin, csharp, first-timers-friendly
|
||||
|
||||
# Either `true` to make the repository private, or `false` to make it public.
|
||||
private: false
|
||||
|
||||
has_issues: true
|
||||
has_projects: false
|
||||
has_wiki: false
|
||||
|
||||
has_downloads: true
|
||||
|
||||
default_branch: master
|
||||
|
||||
allow_squash_merge: true
|
||||
allow_merge_commit: false
|
||||
allow_rebase_merge: false
|
||||
|
||||
# Labels: define labels for Issues and Pull Requests
|
||||
labels:
|
||||
- name: area/automation
|
||||
color: 5DADE2
|
||||
description: Categorizes an issue or PR as relevant to project automation
|
||||
|
||||
- name: area/build
|
||||
color: 5DADE2
|
||||
description: Categorizes an issue or PR as relevant to build infrastructure
|
||||
|
||||
- name: area/community
|
||||
color: 5DADE2
|
||||
description: Categorizes an issue or PR as relevant to community or interactions
|
||||
|
||||
- name: do-not-merge/breaking-change
|
||||
color: E74C3C
|
||||
description: Categorizes issue or PR as related to breaking change to an existing API
|
||||
|
||||
- name: do-not-merge/work-in-progress
|
||||
color: E74C3C
|
||||
description: Indicates that a PR should not merge because it is a work in progress.
|
||||
|
||||
- name: epic
|
||||
color: f9cdb3
|
||||
|
||||
- name: good first issue
|
||||
color: 7057ff
|
||||
description: Denotes an issue ready for a new contributor, according to the "help wanted" guidelines.
|
||||
|
||||
- name: hacktoberfest
|
||||
color: F59B00
|
||||
description: Complete the Hacktoberfest challenge and earn a limited edition T-shirt.
|
||||
|
||||
- name: help wanted
|
||||
color: 008672
|
||||
description: Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.
|
||||
|
||||
- name: invalid
|
||||
color: F59B00
|
||||
description: Ineligible for the Hacktoberfest challenge
|
||||
|
||||
- name: kind/api-change-breaking
|
||||
color: E74C3C
|
||||
description: Categorizes issue or PR as related to breaking change to an existing API
|
||||
|
||||
- name: kind/bug
|
||||
color: d73a4a
|
||||
description: Something isn't working
|
||||
|
||||
- name: kind/cleanup
|
||||
color: 336699
|
||||
description: Categorizes issue or PR as related to cleaning up code, process, or technical debt.
|
||||
|
||||
- name: kind/consumer-experience
|
||||
color: 336699
|
||||
description: Categorizes issue or PR as related to improving the experience of consumers
|
||||
|
||||
- name: kind/contributor-experience
|
||||
color: 336699
|
||||
description: Categorizes issue or PR as related to improving the experience of contributors
|
||||
|
||||
- name: kind/dependency
|
||||
color: 336699
|
||||
description: Categorizes an issue or PR as relevant to 3rd party dependencies that are consumed by this project
|
||||
|
||||
- name: kind/discussion
|
||||
color: fcbb3a
|
||||
|
||||
- name: kind/documentation
|
||||
color: 336699
|
||||
description: Categorizes an issue or PR as relevant to 3rd party dependencies that are consumed by this project
|
||||
|
||||
- name: kind/enhancement
|
||||
color: 28B463
|
||||
description: New feature or request.
|
||||
|
||||
- name: kind/feedback
|
||||
color: f9f486
|
||||
description: Categorizes issue as related to feedback from people are using the project or are considering adoption
|
||||
|
||||
- name: kind/maintainer-experience
|
||||
color: D6EAF8
|
||||
description: Categorizes issue or PR as related to improving the experience of maintainers
|
||||
|
||||
- name: kind/performance
|
||||
color: F4D03F
|
||||
description: Categorizes issue or PR as related to improving performance (allocations/memory/init/etc)
|
||||
|
||||
- name: kind/regression
|
||||
color: E74C3C
|
||||
description: Something was working, now it isn't
|
||||
|
||||
- name: kind/security
|
||||
color: fafc7b
|
||||
description: Categorizes issue or PR as related to security incident or defect
|
||||
|
||||
- name: priority/awaiting-more-evidence
|
||||
color: FDEBD0
|
||||
description: Lowest priority. Possibly useful, but not yet enough support to actually get it done.
|
||||
|
||||
- name: priority/backlog
|
||||
color: F5B041
|
||||
description: Higher priority than priority/awaiting-more-evidence.
|
||||
|
||||
- name: priority/critical-urgent
|
||||
color: E74C3C
|
||||
description: Highest priority. Must be actively worked on as someone's top priority right now.
|
||||
|
||||
- name: priority/important-longterm
|
||||
color: D35400
|
||||
description: Important over the long term, but may not be staffed and/or may need multiple releases to complete.
|
||||
|
||||
- name: priority/important-soon
|
||||
color: D35400
|
||||
description: Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
|
||||
|
||||
- name: triage/duplicate
|
||||
color: BB8FCE
|
||||
description: Indicates an issue is a duplicate of other open issue.
|
||||
|
||||
- name: thank-you
|
||||
color: E45E9D
|
||||
description: Sometimes all a maintainer needs is a “thank you” 🙌.
|
||||
|
||||
- name: triage/most-wanted
|
||||
color: ededed
|
||||
description: Indicates an issue needs more information in order to work on it.
|
||||
|
||||
- name: triage/needs-information
|
||||
color: BB8FCE
|
||||
description: Indicates an issue needs more information in order to work on it.
|
||||
|
||||
- name: triage/not-reproducible
|
||||
color: BB8FCE
|
||||
description: Indicates an issue can not be reproduced as described.
|
||||
|
||||
- name: triage/support
|
||||
color: BB8FCE
|
||||
description: Indicates an issue that is a support question.
|
||||
|
||||
- name: triage/unresolved-or-working-as-intended
|
||||
color: BB8FCE
|
||||
description: Indicates an issue that can not or will not be resolved.
|
||||
|
||||
- name: triage/untriaged
|
||||
color: BB8FCE
|
||||
description: Indicates an issue requires triaging or verification.
|
||||
|
||||
#- name: first-timers-only
|
||||
# include the old name to rename an existing label
|
||||
# oldname: Help Wanted
|
||||
|
||||
branches:
|
||||
- name: master
|
||||
# https://developer.github.com/v3/repos/branches/#update-branch-protection
|
||||
# Branch Protection settings. Set to null to disable
|
||||
protection:
|
||||
# Required. Require at least one approving review on a pull request, before merging. Set to null to disable.
|
||||
required_pull_request_reviews:
|
||||
# The number of approvals required. (1-6)
|
||||
required_approving_review_count: 1
|
||||
# Dismiss approved reviews automatically when a new commit is pushed.
|
||||
dismiss_stale_reviews: true
|
||||
# Blocks merge until code owners have reviewed.
|
||||
require_code_owner_reviews: true
|
||||
# Specify which users and teams can dismiss pull request reviews. Pass an empty dismissal_restrictions object to disable. User and team dismissal_restrictions are only available for organization-owned repositories. Omit this parameter for personal repositories.
|
||||
dismissal_restrictions:
|
||||
users: []
|
||||
teams: []
|
||||
# Required. Require status checks to pass before merging. Set to null to disable
|
||||
required_status_checks:
|
||||
# Required. Require branches to be up to date before merging.
|
||||
strict: true
|
||||
# Required. The list of status checks to require in order to merge into this branch
|
||||
contexts: []
|
||||
# Required. Enforce all configured restrictions for administrators. Set to true to enforce required status checks for repository administrators. Set to null to disable.
|
||||
enforce_admins: null
|
||||
# Required. Restrict who can push to this branch. Team and user restrictions are only available for organization-owned repositories. Set to null to disable.
|
||||
restrictions:
|
||||
users: []
|
||||
teams: []
|
||||
|
|
@ -0,0 +1,330 @@
|
|||
## Ignore Visual Studio temporary files, build results, and
|
||||
## files generated by popular Visual Studio add-ons.
|
||||
##
|
||||
## Get latest from https://github.com/github/gitignore/blob/master/VisualStudio.gitignore
|
||||
|
||||
# User-specific files
|
||||
*.suo
|
||||
*.user
|
||||
*.userosscache
|
||||
*.sln.docstates
|
||||
|
||||
# User-specific files (MonoDevelop/Xamarin Studio)
|
||||
*.userprefs
|
||||
|
||||
# Build results
|
||||
[Dd]ebug/
|
||||
[Dd]ebugPublic/
|
||||
[Rr]elease/
|
||||
[Rr]eleases/
|
||||
x64/
|
||||
x86/
|
||||
bld/
|
||||
[Bb]in/
|
||||
[Oo]bj/
|
||||
[Ll]og/
|
||||
|
||||
# Visual Studio 2015/2017 cache/options directory
|
||||
.vs/
|
||||
# Uncomment if you have tasks that create the project's static files in wwwroot
|
||||
#wwwroot/
|
||||
|
||||
# Visual Studio 2017 auto generated files
|
||||
Generated\ Files/
|
||||
|
||||
# MSTest test Results
|
||||
[Tt]est[Rr]esult*/
|
||||
[Bb]uild[Ll]og.*
|
||||
|
||||
# NUNIT
|
||||
*.VisualState.xml
|
||||
TestResult.xml
|
||||
|
||||
# Build Results of an ATL Project
|
||||
[Dd]ebugPS/
|
||||
[Rr]eleasePS/
|
||||
dlldata.c
|
||||
|
||||
# Benchmark Results
|
||||
BenchmarkDotNet.Artifacts/
|
||||
|
||||
# .NET Core
|
||||
project.lock.json
|
||||
project.fragment.lock.json
|
||||
artifacts/
|
||||
**/Properties/launchSettings.json
|
||||
|
||||
# StyleCop
|
||||
StyleCopReport.xml
|
||||
|
||||
# Files built by Visual Studio
|
||||
*_i.c
|
||||
*_p.c
|
||||
*_i.h
|
||||
*.ilk
|
||||
*.meta
|
||||
*.obj
|
||||
*.iobj
|
||||
*.pch
|
||||
*.pdb
|
||||
*.ipdb
|
||||
*.pgc
|
||||
*.pgd
|
||||
*.rsp
|
||||
*.sbr
|
||||
*.tlb
|
||||
*.tli
|
||||
*.tlh
|
||||
*.tmp
|
||||
*.tmp_proj
|
||||
*.log
|
||||
*.vspscc
|
||||
*.vssscc
|
||||
.builds
|
||||
*.pidb
|
||||
*.svclog
|
||||
*.scc
|
||||
|
||||
# Chutzpah Test files
|
||||
_Chutzpah*
|
||||
|
||||
# Visual C++ cache files
|
||||
ipch/
|
||||
*.aps
|
||||
*.ncb
|
||||
*.opendb
|
||||
*.opensdf
|
||||
*.sdf
|
||||
*.cachefile
|
||||
*.VC.db
|
||||
*.VC.VC.opendb
|
||||
|
||||
# Visual Studio profiler
|
||||
*.psess
|
||||
*.vsp
|
||||
*.vspx
|
||||
*.sap
|
||||
|
||||
# Visual Studio Trace Files
|
||||
*.e2e
|
||||
|
||||
# TFS 2012 Local Workspace
|
||||
$tf/
|
||||
|
||||
# Guidance Automation Toolkit
|
||||
*.gpState
|
||||
|
||||
# ReSharper is a .NET coding add-in
|
||||
_ReSharper*/
|
||||
*.[Rr]e[Ss]harper
|
||||
*.DotSettings.user
|
||||
|
||||
# JustCode is a .NET coding add-in
|
||||
.JustCode
|
||||
|
||||
# TeamCity is a build add-in
|
||||
_TeamCity*
|
||||
|
||||
# DotCover is a Code Coverage Tool
|
||||
*.dotCover
|
||||
|
||||
# AxoCover is a Code Coverage Tool
|
||||
.axoCover/*
|
||||
!.axoCover/settings.json
|
||||
|
||||
# Visual Studio code coverage results
|
||||
*.coverage
|
||||
*.coveragexml
|
||||
|
||||
# NCrunch
|
||||
_NCrunch_*
|
||||
.*crunch*.local.xml
|
||||
nCrunchTemp_*
|
||||
|
||||
# MightyMoose
|
||||
*.mm.*
|
||||
AutoTest.Net/
|
||||
|
||||
# Web workbench (sass)
|
||||
.sass-cache/
|
||||
|
||||
# Installshield output folder
|
||||
[Ee]xpress/
|
||||
|
||||
# DocProject is a documentation generator add-in
|
||||
DocProject/buildhelp/
|
||||
DocProject/Help/*.HxT
|
||||
DocProject/Help/*.HxC
|
||||
DocProject/Help/*.hhc
|
||||
DocProject/Help/*.hhk
|
||||
DocProject/Help/*.hhp
|
||||
DocProject/Help/Html2
|
||||
DocProject/Help/html
|
||||
|
||||
# Click-Once directory
|
||||
publish/
|
||||
|
||||
# Publish Web Output
|
||||
*.[Pp]ublish.xml
|
||||
*.azurePubxml
|
||||
# Note: Comment the next line if you want to checkin your web deploy settings,
|
||||
# but database connection strings (with potential passwords) will be unencrypted
|
||||
*.pubxml
|
||||
*.publishproj
|
||||
|
||||
# Microsoft Azure Web App publish settings. Comment the next line if you want to
|
||||
# checkin your Azure Web App publish settings, but sensitive information contained
|
||||
# in these scripts will be unencrypted
|
||||
PublishScripts/
|
||||
|
||||
# NuGet Packages
|
||||
*.nupkg
|
||||
# The packages folder can be ignored because of Package Restore
|
||||
**/[Pp]ackages/*
|
||||
# except build/, which is used as an MSBuild target.
|
||||
!**/[Pp]ackages/build/
|
||||
# Uncomment if necessary however generally it will be regenerated when needed
|
||||
#!**/[Pp]ackages/repositories.config
|
||||
# NuGet v3's project.json files produces more ignorable files
|
||||
*.nuget.props
|
||||
*.nuget.targets
|
||||
|
||||
# Microsoft Azure Build Output
|
||||
csx/
|
||||
*.build.csdef
|
||||
|
||||
# Microsoft Azure Emulator
|
||||
ecf/
|
||||
rcf/
|
||||
|
||||
# Windows Store app package directories and files
|
||||
AppPackages/
|
||||
BundleArtifacts/
|
||||
Package.StoreAssociation.xml
|
||||
_pkginfo.txt
|
||||
*.appx
|
||||
|
||||
# Visual Studio cache files
|
||||
# files ending in .cache can be ignored
|
||||
*.[Cc]ache
|
||||
# but keep track of directories ending in .cache
|
||||
!*.[Cc]ache/
|
||||
|
||||
# Others
|
||||
ClientBin/
|
||||
~$*
|
||||
*~
|
||||
*.dbmdl
|
||||
*.dbproj.schemaview
|
||||
*.jfm
|
||||
*.pfx
|
||||
*.publishsettings
|
||||
orleans.codegen.cs
|
||||
|
||||
# Including strong name files can present a security risk
|
||||
# (https://github.com/github/gitignore/pull/2483#issue-259490424)
|
||||
#*.snk
|
||||
|
||||
# Since there are multiple workflows, uncomment next line to ignore bower_components
|
||||
# (https://github.com/github/gitignore/pull/1529#issuecomment-104372622)
|
||||
#bower_components/
|
||||
|
||||
# RIA/Silverlight projects
|
||||
Generated_Code/
|
||||
|
||||
# Backup & report files from converting an old project file
|
||||
# to a newer Visual Studio version. Backup files are not needed,
|
||||
# because we have git ;-)
|
||||
_UpgradeReport_Files/
|
||||
Backup*/
|
||||
UpgradeLog*.XML
|
||||
UpgradeLog*.htm
|
||||
ServiceFabricBackup/
|
||||
*.rptproj.bak
|
||||
|
||||
# SQL Server files
|
||||
*.mdf
|
||||
*.ldf
|
||||
*.ndf
|
||||
|
||||
# Business Intelligence projects
|
||||
*.rdl.data
|
||||
*.bim.layout
|
||||
*.bim_*.settings
|
||||
*.rptproj.rsuser
|
||||
|
||||
# Microsoft Fakes
|
||||
FakesAssemblies/
|
||||
|
||||
# GhostDoc plugin setting file
|
||||
*.GhostDoc.xml
|
||||
|
||||
# Node.js Tools for Visual Studio
|
||||
.ntvs_analysis.dat
|
||||
node_modules/
|
||||
|
||||
# Visual Studio 6 build log
|
||||
*.plg
|
||||
|
||||
# Visual Studio 6 workspace options file
|
||||
*.opt
|
||||
|
||||
# Visual Studio 6 auto-generated workspace file (contains which files were open etc.)
|
||||
*.vbw
|
||||
|
||||
# Visual Studio LightSwitch build output
|
||||
**/*.HTMLClient/GeneratedArtifacts
|
||||
**/*.DesktopClient/GeneratedArtifacts
|
||||
**/*.DesktopClient/ModelManifest.xml
|
||||
**/*.Server/GeneratedArtifacts
|
||||
**/*.Server/ModelManifest.xml
|
||||
_Pvt_Extensions
|
||||
|
||||
# Paket dependency manager
|
||||
.paket/paket.exe
|
||||
paket-files/
|
||||
|
||||
# FAKE - F# Make
|
||||
.fake/
|
||||
|
||||
# JetBrains Rider
|
||||
.idea/
|
||||
*.sln.iml
|
||||
|
||||
# CodeRush
|
||||
.cr/
|
||||
|
||||
# Python Tools for Visual Studio (PTVS)
|
||||
__pycache__/
|
||||
*.pyc
|
||||
|
||||
# Cake - Uncomment if you are using it
|
||||
# tools/**
|
||||
# !tools/packages.config
|
||||
|
||||
# Tabs Studio
|
||||
*.tss
|
||||
|
||||
# Telerik's JustMock configuration file
|
||||
*.jmconfig
|
||||
|
||||
# BizTalk build output
|
||||
*.btp.cs
|
||||
*.btm.cs
|
||||
*.odx.cs
|
||||
*.xsd.cs
|
||||
|
||||
# OpenCover UI analysis results
|
||||
OpenCover/
|
||||
|
||||
# Azure Stream Analytics local run output
|
||||
ASALocalRun/
|
||||
|
||||
# MSBuild Binary and Structured Log
|
||||
*.binlog
|
||||
|
||||
# NVidia Nsight GPU debugger configuration file
|
||||
*.nvuser
|
||||
|
||||
# MFractors (Xamarin productivity tool) working folder
|
||||
.mfractor/
|
||||
|
|
@ -0,0 +1,39 @@
|
|||
pull_request_rules:
|
||||
- name: automatic strict merge when CI passes, has 2 reviews, no requests for change and is labeled 'ready-to-merge' unless labelled 'do-not-merge/breaking-change' or 'do-not-merge/work-in-progress'
|
||||
conditions:
|
||||
# Only pull-requests sent to the master branch
|
||||
- base=master
|
||||
|
||||
# All Azure builds should be green:
|
||||
- status-success=Uno.UI - CI
|
||||
|
||||
# CLA check must pass:
|
||||
#- "status-success=license/cla"
|
||||
|
||||
# Note that this only matches people with write / admin access to the repo,
|
||||
# see <https://doc.mergify.io/conditions.html#attribute-list>
|
||||
- "#approved-reviews-by>=2"
|
||||
- "#changes-requested-reviews-by=0"
|
||||
|
||||
# Pull-request must be labeled with:
|
||||
- label=ready-to-merge
|
||||
|
||||
# Do not automatically merge pull-requests that are labelled as do-not-merge
|
||||
# see <https://doc.mergify.io/examples.html#id6>
|
||||
- label!=do-not-merge/breaking-change
|
||||
- label!=do-not-merge/work-in-progress
|
||||
|
||||
# Note: mergify cannot break branch protection rules
|
||||
actions:
|
||||
merge:
|
||||
method: merge
|
||||
# https://doc.mergify.io/strict-workflow.html
|
||||
# https://doc.mergify.io/actions.html#label
|
||||
strict: smart
|
||||
|
||||
- name: automatic merge for allcontributors pull requests
|
||||
conditions:
|
||||
- author=allcontributors[bot]
|
||||
actions:
|
||||
merge:
|
||||
method: merge
|
||||
|
|
@ -0,0 +1,26 @@
|
|||
# Code of Conduct
|
||||
|
||||
This project has adopted the code of conduct defined by the Contributor Covenant to clarify expected behavior in our community. This code of conduct has been adopted by many other open source communities and we feel it expresses our values well.
|
||||
|
||||
As contributors and maintainers of this project, and in the interest of fostering an open and welcoming community, we pledge to respect all people who contribute through reporting issues, posting feature requests, updating documentation, submitting pull requests or patches, and other activities.
|
||||
|
||||
We are committed to making participation in this project a harassment-free experience for everyone, regardless of level of experience, gender, gender identity and expression, sexual orientation, disability, personal appearance, body size, race, ethnicity, age, religion, or nationality.
|
||||
|
||||
Examples of unacceptable behavior by participants include:
|
||||
|
||||
- The use of sexualized language or imagery
|
||||
- Personal attacks
|
||||
- Trolling or insulting/derogatory comments
|
||||
- Public or private harassment
|
||||
- Publishing other's private information, such as physical or electronic addresses, without explicit permission
|
||||
- Other unethical or unprofessional conduct
|
||||
|
||||
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
|
||||
|
||||
By adopting this Code of Conduct, project maintainers commit themselves to fairly and consistently applying these principles to every aspect of managing this project. Project maintainers who do not follow or enforce the Code of Conduct may be permanently removed from the project team.
|
||||
|
||||
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community.
|
||||
|
||||
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting a project maintainer at conduct@platform.uno. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. Maintainers are obligated to maintain confidentiality with regard to the reporter of an incident.
|
||||
|
||||
This Code of Conduct is adapted from the Contributor Covenant, version 1.3.0, available from http://contributor-covenant.org/version/1/3/0/
|
||||
|
|
@ -0,0 +1,209 @@
|
|||
# Uno Platform
|
||||
|
||||
Copyright (c) nventive
|
||||
|
||||
All rights reserved.
|
||||
|
||||
# Apache 2.0 License
|
||||
|
||||
Apache License
|
||||
Version 2.0, January 2004
|
||||
http://www.apache.org/licenses/
|
||||
|
||||
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
||||
|
||||
1. Definitions.
|
||||
|
||||
"License" shall mean the terms and conditions for use, reproduction,
|
||||
and distribution as defined by Sections 1 through 9 of this document.
|
||||
|
||||
"Licensor" shall mean the copyright owner or entity authorized by
|
||||
the copyright owner that is granting the License.
|
||||
|
||||
"Legal Entity" shall mean the union of the acting entity and all
|
||||
other entities that control, are controlled by, or are under common
|
||||
control with that entity. For the purposes of this definition,
|
||||
"control" means (i) the power, direct or indirect, to cause the
|
||||
direction or management of such entity, whether by contract or
|
||||
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
||||
outstanding shares, or (iii) beneficial ownership of such entity.
|
||||
|
||||
"You" (or "Your") shall mean an individual or Legal Entity
|
||||
exercising permissions granted by this License.
|
||||
|
||||
"Source" form shall mean the preferred form for making modifications,
|
||||
including but not limited to software source code, documentation
|
||||
source, and configuration files.
|
||||
|
||||
"Object" form shall mean any form resulting from mechanical
|
||||
transformation or translation of a Source form, including but
|
||||
not limited to compiled object code, generated documentation,
|
||||
and conversions to other media types.
|
||||
|
||||
"Work" shall mean the work of authorship, whether in Source or
|
||||
Object form, made available under the License, as indicated by a
|
||||
copyright notice that is included in or attached to the work
|
||||
(an example is provided in the Appendix below).
|
||||
|
||||
"Derivative Works" shall mean any work, whether in Source or Object
|
||||
form, that is based on (or derived from) the Work and for which the
|
||||
editorial revisions, annotations, elaborations, or other modifications
|
||||
represent, as a whole, an original work of authorship. For the purposes
|
||||
of this License, Derivative Works shall not include works that remain
|
||||
separable from, or merely link (or bind by name) to the interfaces of,
|
||||
the Work and Derivative Works thereof.
|
||||
|
||||
"Contribution" shall mean any work of authorship, including
|
||||
the original version of the Work and any modifications or additions
|
||||
to that Work or Derivative Works thereof, that is intentionally
|
||||
submitted to Licensor for inclusion in the Work by the copyright owner
|
||||
or by an individual or Legal Entity authorized to submit on behalf of
|
||||
the copyright owner. For the purposes of this definition, "submitted"
|
||||
means any form of electronic, verbal, or written communication sent
|
||||
to the Licensor or its representatives, including but not limited to
|
||||
communication on electronic mailing lists, source code control systems,
|
||||
and issue tracking systems that are managed by, or on behalf of, the
|
||||
Licensor for the purpose of discussing and improving the Work, but
|
||||
excluding communication that is conspicuously marked or otherwise
|
||||
designated in writing by the copyright owner as "Not a Contribution."
|
||||
|
||||
"Contributor" shall mean Licensor and any individual or Legal Entity
|
||||
on behalf of whom a Contribution has been received by Licensor and
|
||||
subsequently incorporated within the Work.
|
||||
|
||||
2. Grant of Copyright License. Subject to the terms and conditions of
|
||||
this License, each Contributor hereby grants to You a perpetual,
|
||||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
||||
copyright license to reproduce, prepare Derivative Works of,
|
||||
publicly display, publicly perform, sublicense, and distribute the
|
||||
Work and such Derivative Works in Source or Object form.
|
||||
|
||||
3. Grant of Patent License. Subject to the terms and conditions of
|
||||
this License, each Contributor hereby grants to You a perpetual,
|
||||
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
||||
(except as stated in this section) patent license to make, have made,
|
||||
use, offer to sell, sell, import, and otherwise transfer the Work,
|
||||
where such license applies only to those patent claims licensable
|
||||
by such Contributor that are necessarily infringed by their
|
||||
Contribution(s) alone or by combination of their Contribution(s)
|
||||
with the Work to which such Contribution(s) was submitted. If You
|
||||
institute patent litigation against any entity (including a
|
||||
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
||||
or a Contribution incorporated within the Work constitutes direct
|
||||
or contributory patent infringement, then any patent licenses
|
||||
granted to You under this License for that Work shall terminate
|
||||
as of the date such litigation is filed.
|
||||
|
||||
4. Redistribution. You may reproduce and distribute copies of the
|
||||
Work or Derivative Works thereof in any medium, with or without
|
||||
modifications, and in Source or Object form, provided that You
|
||||
meet the following conditions:
|
||||
|
||||
(a) You must give any other recipients of the Work or
|
||||
Derivative Works a copy of this License; and
|
||||
|
||||
(b) You must cause any modified files to carry prominent notices
|
||||
stating that You changed the files; and
|
||||
|
||||
(c) You must retain, in the Source form of any Derivative Works
|
||||
that You distribute, all copyright, patent, trademark, and
|
||||
attribution notices from the Source form of the Work,
|
||||
excluding those notices that do not pertain to any part of
|
||||
the Derivative Works; and
|
||||
|
||||
(d) If the Work includes a "NOTICE" text file as part of its
|
||||
distribution, then any Derivative Works that You distribute must
|
||||
include a readable copy of the attribution notices contained
|
||||
within such NOTICE file, excluding those notices that do not
|
||||
pertain to any part of the Derivative Works, in at least one
|
||||
of the following places: within a NOTICE text file distributed
|
||||
as part of the Derivative Works; within the Source form or
|
||||
documentation, if provided along with the Derivative Works; or,
|
||||
within a display generated by the Derivative Works, if and
|
||||
wherever such third-party notices normally appear. The contents
|
||||
of the NOTICE file are for informational purposes only and
|
||||
do not modify the License. You may add Your own attribution
|
||||
notices within Derivative Works that You distribute, alongside
|
||||
or as an addendum to the NOTICE text from the Work, provided
|
||||
that such additional attribution notices cannot be construed
|
||||
as modifying the License.
|
||||
|
||||
You may add Your own copyright statement to Your modifications and
|
||||
may provide additional or different license terms and conditions
|
||||
for use, reproduction, or distribution of Your modifications, or
|
||||
for any such Derivative Works as a whole, provided Your use,
|
||||
reproduction, and distribution of the Work otherwise complies with
|
||||
the conditions stated in this License.
|
||||
|
||||
5. Submission of Contributions. Unless You explicitly state otherwise,
|
||||
any Contribution intentionally submitted for inclusion in the Work
|
||||
by You to the Licensor shall be under the terms and conditions of
|
||||
this License, without any additional terms or conditions.
|
||||
Notwithstanding the above, nothing herein shall supersede or modify
|
||||
the terms of any separate license agreement you may have executed
|
||||
with Licensor regarding such Contributions.
|
||||
|
||||
6. Trademarks. This License does not grant permission to use the trade
|
||||
names, trademarks, service marks, or product names of the Licensor,
|
||||
except as required for reasonable and customary use in describing the
|
||||
origin of the Work and reproducing the content of the NOTICE file.
|
||||
|
||||
7. Disclaimer of Warranty. Unless required by applicable law or
|
||||
agreed to in writing, Licensor provides the Work (and each
|
||||
Contributor provides its Contributions) on an "AS IS" BASIS,
|
||||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
||||
implied, including, without limitation, any warranties or conditions
|
||||
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
||||
PARTICULAR PURPOSE. You are solely responsible for determining the
|
||||
appropriateness of using or redistributing the Work and assume any
|
||||
risks associated with Your exercise of permissions under this License.
|
||||
|
||||
8. Limitation of Liability. In no event and under no legal theory,
|
||||
whether in tort (including negligence), contract, or otherwise,
|
||||
unless required by applicable law (such as deliberate and grossly
|
||||
negligent acts) or agreed to in writing, shall any Contributor be
|
||||
liable to You for damages, including any direct, indirect, special,
|
||||
incidental, or consequential damages of any character arising as a
|
||||
result of this License or out of the use or inability to use the
|
||||
Work (including but not limited to damages for loss of goodwill,
|
||||
work stoppage, computer failure or malfunction, or any and all
|
||||
other commercial damages or losses), even if such Contributor
|
||||
has been advised of the possibility of such damages.
|
||||
|
||||
9. Accepting Warranty or Additional Liability. While redistributing
|
||||
the Work or Derivative Works thereof, You may choose to offer,
|
||||
and charge a fee for, acceptance of support, warranty, indemnity,
|
||||
or other liability obligations and/or rights consistent with this
|
||||
License. However, in accepting such obligations, You may act only
|
||||
on Your own behalf and on Your sole responsibility, not on behalf
|
||||
of any other Contributor, and only if You agree to indemnify,
|
||||
defend, and hold each Contributor harmless for any liability
|
||||
incurred by, or claims asserted against, such Contributor by reason
|
||||
of your accepting any such warranty or additional liability.
|
||||
|
||||
END OF TERMS AND CONDITIONS
|
||||
|
||||
APPENDIX: How to apply the Apache License to your work.
|
||||
|
||||
To apply the Apache License to your work, attach the following
|
||||
boilerplate notice, with the fields enclosed by brackets "[]"
|
||||
replaced with your own identifying information. (Don't include
|
||||
the brackets!) The text should be enclosed in the appropriate
|
||||
comment syntax for the file format. We also recommend that a
|
||||
file or class name and description of purpose be included on the
|
||||
same "printed page" as the copyright notice for easier
|
||||
identification within third-party archives.
|
||||
|
||||
Copyright [yyyy] [name of copyright owner]
|
||||
|
||||
Licensed under the Apache License, Version 2.0 (the "License");
|
||||
you may not use this file except in compliance with the License.
|
||||
You may obtain a copy of the License at
|
||||
|
||||
http://www.apache.org/licenses/LICENSE-2.0
|
||||
|
||||
Unless required by applicable law or agreed to in writing, software
|
||||
distributed under the License is distributed on an "AS IS" BASIS,
|
||||
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
||||
See the License for the specific language governing permissions and
|
||||
limitations under the License.
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
# template
|
||||
template for brand new github repositories
|
||||
|
|
@ -0,0 +1,7 @@
|
|||
# Reporting Security Issues
|
||||
|
||||
The Uno team and community take security bugs in Uno seriously. We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.
|
||||
|
||||
To report a security issue, email [security@platform.uno](mailto:security@platform.uno) and include the word "SECURITY" in the subject line.
|
||||
|
||||
The Uno team will send a response indicating the next steps in handling your report. After the initial reply to your report, the security team will keep you informed of the progress towards a fix and full announcement, and may ask for additional information or guidance.
|
||||
Загрузка…
Ссылка в новой задаче