Closed PRemmen closed 9 years ago
The workflow as described sounds good to me.
There is one point to discuss though: IIRC, in annex60, people work on their own fork, where they have all rights, and make a pull request afterwards. In EnEff-BIM, we want a private repository and no public forks, so we are probably going to work in the main repository (but in a separate branch).
(Also discussed here: https://github.com/RWTH-EBC/AixLib/issues/1 )
Adapted Worflow proposal:
This page describes the workflow for changing source code and documentation. Eventually, as the design becomes more stable, we will define a stricter process. At this stage of the development, code changes should be done as follows:
Note that only the person who reviewed the code will merge it to the master. Don't merge your own revisions without having them reviewed.
Thanks for the workflow. That's fine for me!
And thanks for adding the issue labels
I added the workflow to the wiki, but I will leave this issue open for some time, to be reviewed if wanted
https://github.com/EnEff-BIM/EnEffBIM-Framework/wiki/Git-Workflow
Workflow has been discussed at Berlin workshop and can be closed
I think we should add a Git workflow to our wiki, so we maintain a overview what is changed etc.
We could adapt the workflow from the annex repository: https://github.com/iea-annex60/modelica-annex60/wiki/Workflow-for-code-changes
Are there any objections using this workflow and adjust it for our purposes?