Wherever you want to Implement a new feature or Fix a bug (see below) the best way to work with us is to fork the project in your userspace (in GitHub is called https://github.com/<username>) and to Pull-Request on an ad-hoc branch different from the 'develop'
In order to fork, go to the component of your interest and click on "Fork" on the right-top.
Components are:
Once forked, you need to clone your fork on your computer using Git command line or any IDE with Git support (Eclipse, NetBeans, Intelli-J, etc...) using the provided info from the component’s page:
git clone <copied_URL_from_GitHub>
cd <cloned_component_name>
Once cloned, create and switch to an ad-hoc branch related to your issue and start coding!
git checkout -b <my_feature_branch_name>
Naming convention is <issue code>-<issue_or_solution_title>, you can ask Jira to produce one for you (e.g. OP-962-session-table-for-log):
On your "forked-and-cloned-then-branched" you can commit as many times you want, please follow the 'gold rules' below.
Once finished, tested and ready to share, it's time to push! By pushing you will reflect your commits on your online fork. After that you can ask a pull-request toward the ad-hoc branch on the original repository. For better understanding the above and others Git terms you may be helped by this graphical view:
Please refer to Java Spring pattern (see Spring Migration) and use Smart Commits (track your time) as much you can.
Stay tuned!
Very important, keep an eye on new developments landing on the component’s develop branch and periodically resync your fork!
For more info see Git fork syncing (polish your work)
Coding chips!
We need you!
The ticketing version doesn't change anyway: you can contribute through bugs-fixing and feature-requests or even answering to new support-request coming from new users. In order to avoid different devs work on same issues, we kindly ask you to inform us so the task can be assigned to you.
And don't forget the 'gold rules'!
Fork, develop & merge-request (pull-request)
Double analyze the existing code, don't write what is already written, be DRY (Don't Repeat Yourself)
Dumb code is better than clever one when is time to share
Write comments when only "YOU" know what you are doing
Optimize only after achieved
Less is more!
Thanks and happy coding!
Add Comment