Getting started / deploy process #200
Replies: 1 comment 1 reply
-
Sounds like an interesting idea! I haven't used GitHub templates, so I'm not entirely familiar with how they work.
The only advantages I can think of regarding forks are that:
I don't think either of those points are worth hanging on to forks if templates offer an advantage. But we'd probably want to make sure you can still at least pull in updates from upstream. From reading over the templates documentation, I'm not sure whether that's possible. Do you know? |
Beta Was this translation helpful? Give feedback.
-
Continued from #198
I had wondered whether it's worth changing the setup process from forking to setting up the upstream repository as a template repository instead? Given that we'll all have different datasets and orgs we're hosting, I didn't really see a scenario in which forking makes sense for contributing upstream from our own JKAN instances?
Whilst I've not looked in detail, if I understand template repos correctly, I think it's still possible to pull downstream changes from the original template into your instance if you wanted to pull in new changes and bug fixes? This was a short article I found on the topic https://medium.com/geekculture/how-to-use-git-to-downstream-changes-from-a-template-9f0de9347cc2
Beta Was this translation helpful? Give feedback.
All reactions