Submodule for gherkin-c relies on mirror repos which are going away

[mattwynne]

🤔 What's the problem you've observed?

This repo relies on the https://github.com/cucumber/gherkin-c mirror repo, generated from the main https://github.com/cucumber/common repo. We have a strategy (cucumber/common#1550) to retire these mirror repos and the infrastructure that maintains them.

✨ Do you have a proposal for making it better?

Once the Gherkin project has been moved out of the monorepo, we'll need to either update it to continue publishing a mirror repo of gherkin-c, or ideally we'd change this project to be able to handle a submodule that contains the whole gherkin project. It seems that would be simpler.

📚 Any additional context?

https://github.com/orgs/cucumber/projects/12

---

This text was originally generated from a template, then edited by hand. You can modify the template here.

[tmcgilchrist]

#41 switches to the main https://github.com/cucumber/common repo.

[mattwynne]

@tmcgilchrist thanks, but I think there's been a misunderstanding. The code for gherkin has moved into the https://github.com/cucumber/gherkin repo

[tmcgilchrist]

Yes of course, that is the repo I’m using in the PR.

…

On Thu, 1 Dec 2022 at 9:08 am, Matt Wynne ***@***.***> wrote: @tmcgilchrist <https://github.com/tmcgilchrist> thanks, but I think there's been a misunderstanding. The code for gherkin has moved into the https://github.com/cucumber/gherkin repo — Reply to this email directly, view it on GitHub <#39 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABJXOK7OREB32UTZ3FUMVLWK7F55ANCNFSM56JIMKCA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mpkorstanje]

Resolved by #41.

@mattwynne the PR had the correct url, the url in the message was a typo.