Separate git repo for each language?

[aslakhellesoy]

Node.js' npm and PHP's Composer require packages/modules to be defined in the root of a repo. -At least if they are to be consumed as git repos. See #4 and #9 for more details.

My only reservation about splitting this repo into several repos (gherkin-csharp, gherkin-golang etc) is that it might make it more difficult to keep the implementations in sync. But maybe not.

All the language-specific repos would be "linked" to this repo using git submodule (or something similar), and maybe it wouldn't be that much of an issue.

WDYT?

[everzet]

How about subtree splits: https://help.github.com/articles/splitting-a-subfolder-out-into-a-new-repository/ ?

[muhqu]

I like the subtree split idea. it shouldn't be pain when you think of the subtree split repository as some kind of release artifact. Like you would package software for download, you would push squashed changes to the split tree repository...

I just added a sample push-release target to the golang/Makefile... I temporarily pushed the changes to https://github.com/muhqu/go-gherkin3 ...

[mattwynne]

A thousand times yes. This will help keep things sustainable as we add more languages.

If we keep a master repo that includes all the language implementations as submodules, that will make it easier for people who hack on multiple language versions, and we can also have one travis build for that repo to show that everything's working across languages. Maybe a bit like https://github.com/rspec/rspec-dev?

Seems to me the submodule repo names shout be gherkin3-go gherkin3-ruby etc to keep them sitting next to each other.

[muhqu]

Fine with me, too.

[aslakhellesoy]

Cool. Let's name them gherkin-ruby, gherkin-go etc, without the 3 in the name.

[chmontgomery]

👍

[aslakhellesoy]

Ok folks, I have split the subfolders into separate repositories:

• https://github.com/cucumber/gherkin-csharp
• https://github.com/cucumber/gherkin-go
• https://github.com/cucumber/gherkin-java
• https://github.com/cucumber/gherkin-javascript
• https://github.com/cucumber/gherkin-ruby

I'm working on git subtrees next, and updating the build scripts.

[aslakhellesoy]

Allright - it's all reorganised now. See CONTRIBUTING.md - the beginning of the file describes how this new subtree stuff works.

@muhqu your push-release target seems redundant now that there is add-remotes and push-subtrees targets in the root Makefile.

[aslakhellesoy]

Allright - this is now done. It doesn't change much to the workflow. Keep working in this repo and do the occasional make push-subtrees.