同步操作将从 Gitee 极速下载/Gravitee-API-Gateway 强制同步,此操作会覆盖自 Fork 仓库以来所做的任何修改,且无法恢复!!!
确定后同步将在后台操作,完成时将刷新页面,请耐心等待。
You think Gravitee.io is awesome and want to contribute to the project? Here are few guidelines that should help you get started.
We use GitHub issues to track bugs and enhancements. Find a bug in the source code? Want to propose new features or enhancements? You can help us by submitting an issue in our repository. Before you submit your issue, search the issues archive or the backlog; maybe your question was already answered.
Issues are only to report bugs, request enhancements, or request new features. For general questions and discussions, use the Gravitee.io Gitter chat.
Providing the following information will help us deal quickly with your issue :
Overview of the issue : describe the issue and why this is a bug for you.
Gravitee.io version(s) : possible regression?
Browsers and Operating System : Linux/Windows/Docker? Browser version for the UI, etc …
You have stack trace, screenshots, logs? add these to the issue’s description.
You’ve submitted an issue to the project and know how to fix it? You can contribute to the project by forking the repository and submitting your pull requests.
Before you submit your pull request consider the following guidelines:
Make your changes in a new git branch:
git checkout -b issue/#<issue-id>-my-fix-branch master
Note : issue-id reference the id generated by GitHub (#issue-id).
Create your patch, including appropriate test cases.
Update the documentation if you create new features or think the documentation needs to be updated/completed.
Commit your changes using a descriptive commit message.
git commit -a
Build your changes locally to ensure all the tests pass:
mvn clean install
Push your branch to GitHub:
git push origin issue/#<issue-id>-my-fix-branch
In GitHub, send a pull request to <gravitee-io/gravitee-gateway>:master
.
If we suggest changes then:
Make the required updates.
Re-run the test suite to ensure tests are still passing.
Commit your changes to your branch (e.g. issue/<issue-id>-my-fix-branch
).
Push the changes to your GitHub repository (this will update your Pull Request).
If the PR gets too outdated we may ask you to rebase and force push to update the PR:
git rebase master
git push origin issue/#<issue-id>-my-fix-branch -f
And That’s it! You’ve just contributed to the project and we really appreciate it ! You can still find help, news and information on our forum.
Please sign our Contributor License Agreement (CLA) and send it to contact@graviteesource.com. For any code changes to be accepted, the CLA must be signed.
You can find more detailed information about contributing in the Github guides.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。