Hi Han,
I'm not sure exactly what you would like. For the EPICS areaDetector
project there is a Github workflow guide here:
https://github.com/areaDetector/areaDetector/wiki/areaDetector-Git-Workflows
It is probably always a good idea to talk to the main developers
early. If you are doing a small patch then cloning and doing a pull
request back to the master branch is a typical workflow. But if you
are doing some major change then the developer will probably want to
create a branch for you and other developers to work on, and then you
do pull requests back to that branch.
Mark
-----Original Message----- From: [email protected]
[mailto:[email protected]] On Behalf Of Jeong Han Lee
Sent: Monday, February 15, 2016 2:47 PM To: [email protected]
Subject: Guide needed in order to work with the EPICS related Git
repositories
Hi,
I would like to have a *nice* guide, which is always I could get in
here, in order to work with the EPICS related Git repositories at
github.com.
Is there any procedure which I should follow in order to do any pull
requests? Should it be better to talk plan to main developers or
maintainers before forking, doing pull requests, or both?
It looks like to add more features in some existent projects in near
future, but I don't have clear idea how to do this. Please guide me
to minimize any difficulties.
Thanks, Han