This action will force synchronization from apioak/apioak, which will overwrite any changes that you have made since you forked the repository, and can not be recovered!!!
Synchronous operation will process in the background and will refresh the page when finishing processing. Please be patient.
You can contribute to the APIOAK project in the following forms.
Report bugs or usage issues via Issues
for us to fix.
Contribute code, documentation or test cases for APIOAK via Pull Request
.
Search through Issues The issue does not exist.
Open New Issues and briefly describe the issue in the title. Describe the detailed version, operating environment, and logs and other information in the content.
Before new features are developed or problems are discovered, they can be announced or reported through the Issues
method.
If you are contributing code for APIOAK for the first time, you need to click the Fork
button in the upper right
corner of the project homepage to put the project Fork
in your home directory.
Clone items in home directory to local.
git clone https://github.com/{username}/apioak.git
git remote add upstream https://github.com/apioak/apioak.git
git checkout -b feature/add/contributing/document upstream/master
git add feature/file.lua
git commit -m "feature: add contributing document."
git push origin feature/add/contributing/document
After the submission is successful, launch Pull Request
to the main project on the homepage of the home directory
project.
When initiating Pull Request
to the trunk, if the problem has been announced in the Issues
, you can fill it
in the Pull Request
fill-in, FIX # ISSUES_ID
, You can associate with Issues, and automatically close Issues
after Pull Request Merged.
此处可能存在不合适展示的内容,页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容,可点击提交进行申诉,我们将尽快为您处理。