Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add de facto rules #5

Closed
wants to merge 1 commit into from
Closed

add de facto rules #5

wants to merge 1 commit into from

Conversation

mburns
Copy link
Member

@mburns mburns commented Jul 13, 2015

I figured we should start somewhere...

fixes #2

@guilhem
Copy link
Member

guilhem commented Jul 14, 2015

global 👍 :)

I only have some comment about develop branch. I not quite a huge fan of this workflow and I don't think we have cookbooks with it.

If I remember well, it's you @BarthV who talk first about develop pattern. Can you explain more? :)

@BarthV
Copy link
Member

BarthV commented Aug 2, 2015

I like to say "Use develop branch wherever it exists"

So if there is no develop branch no need to create one. The releases tempo is very slow so we don't really need a dev branch I think. But It still a good idea to use one when it's needed.

It depends on the project activity I think.

@mburns
Copy link
Member Author

mburns commented Aug 26, 2015

It depends on the project activity I think.

Maybe the 'rule' should be generalized. "Follow each repo's guidelines for contributing" or somesuch. That would cover individual styleguides, test coverage, branch/release process, etc

@mburns mburns closed this Aug 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Write "Our Rules" page
3 participants