Please fee free to report bugs, submit suggestions, or submit PRs according to this guide.
Before submitting your issues, please go through a comprehensive search to make sure the problem cannot be solved just by searching.
Check the Issue List to make sure the problem is not repeated.
Create a new issue and choose the type of issue.
Define the issue with a clear and descriptive title.
Fill in necessary information according to the template.
Choose a label after issue created.
Please pay attention to your issue, you may need provide more information during discussion.
Fork the Apache APISIX repo to your own repo to work, then setting proper upstream.
git remote add upstream https://github.com/apache/apisix.git
Please choose your target issue. If it is a new issue discovered or a new function enhancement to offer, please create an issue and set the right label for it.
After choosing the relevant issue, please reply with a deadline to indicate that you are working on it.
Find a mentor from the Team page and your mentor will give you feedback about your PR or issue in time.
Good First Issue curates easy pickings from this project, and helps you make your first contribution to Apache APISIX®.
- Apache APISIX®
- Apache APISIX® Ingress Controller
- Apache APISIX® dashboard
- Apache APISIX® Helm Chart
- Docker distribution for Apache APISIX®
- Apache APISIX® Website
- Apache APISIX® Java Plugin Runner
- Apache APISIX® Go Plugin Runner
Switch to your forked master branch, pull codes from upstream, then create a new branch.
$ git checkout master$ git pull upstream master$ git checkout -b IssueNo
Notice: We will merge PR using squash, commit logs will be different form upstream if you use one older branch.
Please obey the Code of Conduct during the process of development and finish the check before submitting the pull request.
Then push codes to your fork repo.
$ git add modified-file-names$ git commit -m 'commit message'$ git push origin issueNo
Send a pull request to the master branch.
The mentor will do codes review before discussing some details (including the design, the implementation and the performance) with you.
Also make sure that the pull request title has a semantic prefix like
feat:or any other conventional commit types.
Then congratulate to you to be an official contributor of Apache APISIX.
You can delete the remote branch (origin/IssueNo) and the local branch (IssueNo) associated with the remote branch (origin/IssueNo) after the mentor merged the PR into the master branch.
$ git checkout master$ git branch -d IssueNo$ git push origin --delete issueNo
Please note that in order to show your ID in the contributor list, please DO NOT forget to set the configurations below:
$ git config --global user.name "username"$ git config --global user.email "mail address"