Forums / Developer / Participate on the Tracker, through GIT, how?

"Please Note:
  • At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
  • This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Participate on the Tracker, through GIT, how?

Author Message

Robin Muilwijk

Sunday 27 February 2011 10:56:23 am

Hi,

Anyone from Engineering that can give me an idea on how a community members could participate on the issue tracker through GIT.

For example; he/she spots an issue, and got a possible fix for it. Does he/she fork on GIT, and create separate branches for each issue, then apply the fix, and do a pull request? So one branch and pull request for a single issue? Or is this done in another way?

Thanks Robin

Board member, eZ Publish Community Project Board - Member of the share.ez.no team - Key values: Openness and Innovation.

LinkedIn: http://nl.linkedin.com/in/robinmuilwijk // Twitter: http://twitter.com/i_robin // Skype: robin.muilwijk

Carlos Revillo

Sunday 27 February 2011 1:17:44 pm

Hi Robin.

Actually this is the way me an other people are working. So i would say yes. a branch for each issue is good.

André R.

Monday 28 February 2011 1:50:42 am

This is defined in the GIT article as previewed here:

https://docs.google.com/a/ez.no/document/d/1Xm2NIznsHS1n64aEOG1lrj4nz6souZ4Mi4guPJoNr48/edit?hl=en&authkey=CKbN594J#

"A topic branch is a branch specifically created for an issue or a collection of related issues, or even a new feature. From a SVN background this might sound crazy. But with GIT, branching is cheap and makes the whole process simpler, retains history and allows online reviews on github."

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Bertrand Dunogier

Wednesday 02 March 2011 6:43:32 am

I can confirm what André says. Branches in GIT are cheap, easy to use, and a hard requirement if you wanna send a clean pull request.

Bertrand Dunogier
eZ Systems Engineering, Lyon
http://twitter.com/bdunogier
http://gplus.to/BertrandDunogier

Robin Muilwijk

Wednesday 02 March 2011 11:23:49 am

Thanks for the feedback all! Also re-read the GIT tutorial (how could I forget about that one?), and it's all clear. Branches seems very easy, and clean indeed.

Thanks, Robin

Board member, eZ Publish Community Project Board - Member of the share.ez.no team - Key values: Openness and Innovation.

LinkedIn: http://nl.linkedin.com/in/robinmuilwijk // Twitter: http://twitter.com/i_robin // Skype: robin.muilwijk