All files in the pulsar-translation repository are written in Markdown. If you do not know how to use Markdown, learn how to get started.
- Visit https://github.com/apache/pulsar-translation
- Click
Fork
button (top right) to establish a cloud-based fork.
Create your clone.
$ cd $working_dir
$ git clone https://github.com/$user/pulsar-translation
Set your clone to track upstream repository.
$ cd $working_dir/pulsar-translation
$ git remote add upstream https://github.com/apache/pulsar-translation.git
Use the git remote -v
command, you find the output looks as follows:
origin https://github.com/$user/pulsar-translation.git (fetch)
origin https://github.com/$user/pulsar-translation.git (push)
upstream https://github.com/apache/pulsar-translation (fetch)
upstream https://github.com/apache/pulsar-translation (push)
Get your local master up to date.
$ cd $working_dir/pulsar-translation
$ git checkout master
$ git fetch upstream
$ git rebase upstream/master
$ git push origin master
Branch from master.
$ git checkout -b myfeature
You can now edit the code on the myfeature
branch.
Commit your changes.
$ git add <filename>
$ git commit -m "$add a comment"
Likely you'll go back and edit-build-test in a few cycles.
The following commands might be helpful for you.
$ git add <filename> (used to add one file)
git add -A (add all changes, including new/delete/modified files)
git add -a -m "$add a comment" (add and commit modified and deleted files)
git add -u (add modified and deleted files, not include new files)
git add . (add new and modified files, not including deleted files)
When your commit is ready for review (or just to establish an offsite backup of your work), push your branch to your fork on github.com
:
$ git push origin myfeature
- Visit your fork at https://github.com/$user/pulsar-translation (replace
$user
obviously). - Click the
Compare & pull request
button next to yourmyfeature
branch.
Once you open your pull request, at least two reviewers will participate in reviewing. Those reviewers will conduct a thorough code review, looking for correctness, bugs, opportunities for improvement, documentation and comments, and style.
Commit changes made in response to review comments to the same branch on your fork.
Very small PRs are easy to review. Very large PRs are very difficult to review.