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' (if not available please ask on Jira OpenHospital page to open one for you).
In order to fork, go to the develop branch page and 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...) . Once cloned (or synced), switch to the 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 task 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-branchthen-branched" you can commit as many times you want, but 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. If you need to resync your fork because too old, please follow
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!
| Child pages (Children Display) | ||||||
|---|---|---|---|---|---|---|
|
...