We'd love for you to contribute to our source code and to make reactiveui even better than it is today! Here are the guidelines we'd like you to follow:
If you have questions about how to use reactiveui, please direct these to StackOverflow. The project maintainers hang out in this Slack channel.
If you find a bug in the source code or a mistake in the documentation, you can help us by submitting an issue to our GitHub Repository. Even better you can submit a Pull Request with a fix.
Please see the Submission Guidelines below.
You can request a new feature by submitting an issue to our GitHub Repository. If you would like to implement a new feature then consider what kind of change it is:
If your issue appears to be a bug, and hasn't been reported, open a new issue. Help us to maximize the effort we can spend fixing issues and adding new features, by not reporting duplicate issues.
Providing the following information will increase the chances of your issue being dealt with quickly:
If you get help, help others. Good karma rulez!
Before you submit your pull request consider the following guidelines:
Search GitHub for an open or closed Pull Request that relates to your submission. You don't want to duplicate effort.
Make your changes in a new git branch:
git checkout -b my-fix-branch master
Create your patch, including appropriate test cases.
Follow our Coding Rules.
Run the test suite, as described below.
Commit your changes using a descriptive commit message that follows our commit message guidelines.
git commit -a
Note: the optional commit -a
command line option will automatically "add" and "rm" edited files.
Build your changes locally to ensure all the tests pass by using the Solution (.sln) files in the src
directory.
Push your branch to GitHub:
git push origin my-fix-branch
In GitHub, send a pull request to reactiveui:master
.
If we suggest changes, then:
my-fix-branch
).If the PR gets too outdated we may ask you to rebase and force push to update the PR:
git rebase master -i
git push origin my-fix-branch -f
WARNING: Squashing or reverting commits and force-pushing thereafter may remove GitHub comments on code that were previously made by you or others in your commits. Avoid any form of rebasing unless necessary.
That's it! Thank you for your contribution!
After your pull request is merged, you can safely delete your branch and pull the changes from the main (upstream) repository:
Delete the remote branch on GitHub either through the GitHub web UI or your local shell as follows:
git push origin --delete my-fix-branch
Check out the master branch:
git checkout master -f
Delete the local branch:
git branch -D my-fix-branch
Update your master with the latest upstream version:
git pull --ff upstream master
Once all the above are set up, use the desired Solution (.sln) file in the repository's src
directory.
To ensure consistency throughout the source code, keep these rules in mind as you are working:
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。