This repository has been archived by the owner on Oct 23, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 106
Code Review Process
U. Artie Eoff edited this page Nov 15, 2017
·
7 revisions
-
start work on libyami by 'fork' it to your home
-
commit/push to your home's repo, test it on ubuntu/centos
- please reference any issues in your git commit message body (https://help.github.com/articles/closing-issues-using-keywords/)
-
create 'pull requests'
-
wait for other's review
-
update your home's repo following feedbacks
we recommend force update to avoid unnecessary commit history, your pull requests get update automatically. -
repeat the above two steps until no disagree
-
you can integrate your patch (home repo) with the condition met:
- 1+ member flags ok when patches are less than 50 lines.
- 2+ members flag ok when patches are more than 50 lines
- at least one work day passed after latest patch update
- 1+ member flags ok when patches are less than 50 lines.
-
integrate the patches manually (NOT the button on web page)
-
git push [email protected]/01org/libyami.git HEAD:apache
we do not use the 'Merge pull request' button on web page, because:
- it creates redundant commit log.
- it creates unclear parent-child relation between commits when two merge requests basing on unique commit id.
-
-
now, the pull request is automatically close on web page.