You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 27, 2020. It is now read-only.
I want to help you by contributing to this project, what's the right contribute work flow in use on this project?
I don't see a develop branch dedicated to merge pull request from contributors?
I suppose that the Dropzone_integration branch was dedicated for merge contributor works but this branch was behind the master over 21 commits... can you explain the semantic of this branch?
So I've decide to fork this project create a develop branch on my fork, add a little fix and send a pull request to you on the master branch.
I can help you to industrialize this part and we can introduce a standardized git flow for every contributors.
Do not hesitate to ask me a question for more informations.
The text was updated successfully, but these errors were encountered:
4383
changed the title
Contribute workflow
Contribution workflow
Sep 11, 2017
Hi 4383, i don't think there is a "worflow" yet. I dont really work anymore on this project, seems the recalbox team is keeping it alive on their own branch instead of master.
First thing to do should be to talk with the team on IRC irc.freenode.net/8001 channel : #recalbox or at least on forum: https://forum.recalbox.com/
Hello guys
I want to help you by contributing to this project, what's the right contribute work flow in use on this project?
I don't see a develop branch dedicated to merge pull request from contributors?
I suppose that the Dropzone_integration branch was dedicated for merge contributor works but this branch was behind the master over 21 commits... can you explain the semantic of this branch?
So I've decide to fork this project create a develop branch on my fork, add a little fix and send a pull request to you on the master branch.
I can help you to industrialize this part and we can introduce a standardized git flow for every contributors.
Do not hesitate to ask me a question for more informations.
The text was updated successfully, but these errors were encountered: