forked from microsoft/calculator
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
456fe5e
commit c13b8a0
Showing
822 changed files
with
276,650 additions
and
75 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,11 @@ | ||
| ## IDE-independent coding style via EditorConfig: http://editorconfig.org/ | ||
|
|
||
| root = true | ||
|
|
||
| [*] | ||
| indent_style = space | ||
| indent_size = 4 | ||
| end_of_line = crlf | ||
| charset = utf-8 | ||
| trim_trailing_whitespace = true | ||
| insert_final_newline = true |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,63 @@ | ||
| ############################################################################### | ||
| # Set default behavior to automatically normalize line endings. | ||
| ############################################################################### | ||
| * text=auto | ||
|
|
||
| ############################################################################### | ||
| # Set default behavior for command prompt diff. | ||
| # | ||
| # This is need for earlier builds of msysgit that does not have it on by | ||
| # default for csharp files. | ||
| # Note: This is only used by command line | ||
| ############################################################################### | ||
| *.cs diff=csharp | ||
|
|
||
| ############################################################################### | ||
| # Set the merge driver for project and solution files | ||
| # | ||
| # Merging from the command prompt will add diff markers to the files if there | ||
| # are conflicts (Merging from VS is not affected by the settings below, in VS | ||
| # the diff markers are never inserted). Diff markers may cause the following | ||
| # file extensions to fail to load in VS. An alternative would be to treat | ||
| # these files as binary and thus will always conflict and require user | ||
| # intervention with every merge. To do so, just uncomment the entries below | ||
| ############################################################################### | ||
| *.sln merge=binary | ||
| *.csproj merge=binary | ||
| *.vbproj merge=binary | ||
| *.vcxproj merge=binary | ||
| *.vcproj merge=binary | ||
| *.dbproj merge=binary | ||
| *.fsproj merge=binary | ||
| *.lsproj merge=binary | ||
| *.wixproj merge=binary | ||
| *.modelproj merge=binary | ||
| *.sqlproj merge=binary | ||
| *.wwaproj merge=binary | ||
|
|
||
| ############################################################################### | ||
| # behavior for image files | ||
| # | ||
| # image files are treated as binary by default. | ||
| ############################################################################### | ||
| *.jpg binary | ||
| *.png binary | ||
| *.gif binary | ||
|
|
||
| ############################################################################### | ||
| # diff behavior for common document formats | ||
| # | ||
| # Convert binary document formats to text before diffing them. This feature | ||
| # is only available from the command line. Turn it on by uncommenting the | ||
| # entries below. | ||
| ############################################################################### | ||
| *.doc diff=astextplain | ||
| *.DOC diff=astextplain | ||
| *.docx diff=astextplain | ||
| *.DOCX diff=astextplain | ||
| *.dot diff=astextplain | ||
| *.DOT diff=astextplain | ||
| *.pdf diff=astextplain | ||
| *.PDF diff=astextplain | ||
| *.rtf diff=astextplain | ||
| *.RTF diff=astextplain |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,6 @@ | ||
| # Code of Conduct | ||
|
|
||
| This project has adopted the [Microsoft Open Source Code of Conduct](https://opensource.microsoft.com/codeofconduct/). | ||
| For more information see the [Code of Conduct FAQ](https://opensource.microsoft.com/codeofconduct/faq/) | ||
| or contact [opencode@microsoft.com](mailto:opencode@microsoft.com) with any additional questions or | ||
| comments. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,96 @@ | ||
| # Contributing to Calculator | ||
| The Calculator team encourages community feedback and contributions. Thank you for your interest in | ||
| making Calculator better! There are several ways you can get involved. | ||
|
|
||
| ## Reporting issues and suggesting new features | ||
| If Calculator is not working properly, please file a report in the [Feedback Hub](https://insider.windows.com/en-us/fb/?contextid=130&newFeedback=True). | ||
| Feedback Hub reports automatically include diagnostic data, such as the version of Calculator | ||
| you're using. | ||
|
|
||
| We are happy to hear your ideas for the future of Calculator. Check the | ||
| [Feedback Hub](https://insider.windows.com/en-us/fb/?contextid=130) and see if others have | ||
| submitted similar feedback. You can upvote existing feedback or submit a new suggestion. | ||
|
|
||
| We always look at upvoted items in Feedback Hub when we decide what to work on next. We read the | ||
| comments in both Feedback Hub and GitHub, and we look forward to hearing your input. Remember that | ||
| all community interactions must abide by the [Code of Conduct](CODE_OF_CONDUCT.md). | ||
|
|
||
| ## Finding issues you can help with | ||
| Looking for something to work on? | ||
| [Issues marked *up for grabs*](https://microsoft.com/#TODO_MIGRATE_THIS_LINK_AFTER_GITHUB_MIGRATION) | ||
| are a good place to start. | ||
|
|
||
| Another way you can help is by reproducing issues others have reported. | ||
| [Issues marked *more info needed*](https://microsoft.com/#TODO_MIGRATE_THIS_LINK_AFTER_GITHUB_MIGRATION) | ||
| don't have all the information needed to take action. You can try to reproduce the issue on your | ||
| machine and add more details so we can take action on the report. | ||
|
|
||
| ## Contributions we accept | ||
| We welcome your contributions to the Calculator project, especially to fix bugs and to make | ||
| improvements which address the top issues reported by Calculator users. | ||
|
|
||
| We have a high bar for new features and changes to the user experience. We prefer to evaluate | ||
| *prototypes* to ensure that the design meets users' needs before we start discussing implementation | ||
| details and reviewing code. We follow a [user-centered process for developing features](docs/NewFeatureProcess.md). | ||
| New features need sponsorship from the Calculator team, but we welcome community contributions at | ||
| many stages of the process. | ||
|
|
||
| ## Making changes to the code | ||
|
|
||
| ### Preparing your development environment | ||
| To learn how to build the code and run tests, follow the instructions in the [README](README.md). | ||
|
|
||
| ### Style guidelines | ||
| The code in this project uses several different coding styles, depending on the age and history of | ||
| the code. Please attempt to match the style of surrounding code as much as possible. In new | ||
| components, prefer the patterns described in the [C++ core guidelines](http://isocpp.github.io/CppCoreGuidelines/CppCoreGuidelines) | ||
| and the [modern C++/WinRT language projections](https://docs.microsoft.com/en-us/windows/uwp/cpp-and-winrt-apis/). | ||
|
|
||
| ### Testing | ||
| Your change should include tests to verify new functionality wherever possible. Code should be | ||
| structured so that it can be unit tested independently of the UI. [Manual test cases](docs/ManualTests.md) | ||
| should be used where automated testing is not feasible. | ||
|
|
||
| ### Git workflow | ||
| Calculator uses the [GitHub flow](https://guides.github.com/introduction/flow/) where most | ||
| development happens directly on the `master` branch. The `master` branch should always be in a | ||
| healthy state which is ready for release. | ||
|
|
||
| If your change is complex, please clean up the branch history before submitting a pull request. | ||
| You can use [git rebase](https://docs.microsoft.com/en-us/azure/devops/repos/git/rebase#squash-local-commits) | ||
| to group your changes into a small number of commits which we can review one at a time. | ||
|
|
||
| When completing a pull request, we will generally squash your changes into a single commit. Please | ||
| let us know if your pull request needs to be merged as separate commits. | ||
|
|
||
| ## Submitting a pull request and participating in code review | ||
| Writing a good description for your pull request is crucial to help reviewers and future | ||
| maintainers understand your change. More detail is better. | ||
| - [Link the issue you're addressing in the pull request](https://github.com/blog/957-introducing-issue-mentions). | ||
| - Describe *why* the change is being made and *why* you've chosen a particular solution. | ||
| - Describe any manual testing you performed to validate your change. | ||
|
|
||
| Please submit one pull request per issue. Large pull requests which have unrelated changes can be | ||
| difficult to review. | ||
|
|
||
| After submitting a pull request, members of the calculator team will review your code. We will | ||
| assign the request to an appropriate reviewer within two days. Any member of the community may | ||
| participate in the review, but at least one member of the Calculator team will ultimately approve | ||
| the request. | ||
|
|
||
| Often, multiple iterations will be needed to responding to feedback from reviewers. Try looking at | ||
| [past pull requests](https://microsoft.com/#TODO_MIGRATE_THIS_LINK_AFTER_GITHUB_MIGRATION) to see | ||
| what the experience might be like. | ||
|
|
||
| ## Contributor License Agreement | ||
| Before we can review and accept a pull request from you, you'll need to sign a Contributor License | ||
| Agreement (CLA). The CLA ensures that the community is free to use your contributions. More | ||
| information about the agreement is available on the [Microsoft web site](https://cla.opensource.microsoft.com/). | ||
| Signing the CLA is an automated process, and you only need to do it once for Microsoft projects on | ||
| GitHub. | ||
|
|
||
| You don't need to sign a CLA until you're ready to create a pull request. When your pull request is | ||
| created, it is classified by a bot. If the change is trivial (i.e. you just fixed a typo) then the | ||
| bot will label the PR `cla-not-required`. Otherwise, it's classified as `cla-required`. In that | ||
| case, the system will also tell you how you can sign the CLA. Once you have signed a CLA, the | ||
| current and all future pull requests will be labeled as `cla-signed`. |
Oops, something went wrong.