-
Notifications
You must be signed in to change notification settings - Fork 35
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
GTD-1: Added enable_search option to template #156
Conversation
template/Gemfile
Outdated
@@ -10,3 +10,6 @@ gem 'tzinfo-data', platforms: [:mswin, :mingw, :jruby] | |||
|
|||
# Include the tech docs gem | |||
gem 'govuk_tech_docs' | |||
|
|||
# Overrride middleman-search with our fork. | |||
gem 'middleman-search', :git => "git://github.com/alphagov/middleman-search.git" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we have to use a fork long term?
Looking into it seems we're caught because they've not managed to get manastech/middleman-search#24 merged and a new release :( I wonder if we want to update the comment here to explain why it's a fork since if I understand right you'll get this in every repo that starts from this?
Also any reason why we don't want this to be required by govuk_tech_docs themselves than here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, good idea. I've added a link to the PR as a comment.
It seems that adding this line to the tech docs gem is not effective. It has to be added to the main project.
@kevindew I've added a comment now. Thanks for the feedback. |
@kevindew are you happy to approve? |
@lewisnyman no problem. Re
I see, I'm guessing this is because we can't specify a fork in https://github.com/alphagov/tech-docs-gem/blob/master/govuk_tech_docs.gemspec#L32? This seems to create a strange situation where we need to treat this gem separately? Have we considered publishing the fork to resolve this? I'll approve this now but it'd be good to get the gem situation resolved. |
Not really, I don't feel like that's a decision I can make and I haven't raised it more widely yet. If we have to continue maintaining this fork for a substantial amount of time it feels like a logical next step. Thanks for reviewing! |
See: alphagov/tech-docs-gem#28