13 Aug

Weekly Update 114: The importance of IA pages

This is a copy of our weekly newsletter for developers which you can subscribe to here.

Hello contributors,

As you know, we have a public list of all live Instant Answers, from cheat sheets to interactive tools, from converters to entertainment data, and more. But did you know that as a contributor to an Instant Answer (IA), you have access not just to that IA's traffic data but also to updating its information?

The information stored in these pages is very important and increasingly used to keep metadata separate from Instant Answer code, such as data source, example queries and topics. We also use some of this data to power automated features like the screenshot tool.

So if there are IAs you've contributed to, please log in to their IA pages and take a moment to check the data in them, updating them if necessary. This makes sure they all work as intended and users get the most out of them.

And if you haven't been able to contribute yet, below are some ideas to get you started...

5-minute Fixes

More quick fix ideas here...

Weekend Warriors

More high priority fix ideas here...

IAs for Adoption

The following Instant Answers are looking for a maintainer — someone to moderate suggested changes from the community as well as address any issues that pop up in the future. If you'd like to step forward, please create an issue on GitHub using the button at the bottom of each IA page.

Quick Tip

Last time we looked at fixing unneeded files in a pull request, but what about unneeded files when just pulling down files? Before creating a new branch it's a good idea to get the latest version of an upstream repository, but sometimes new or edited local files prevent it. You're happy overwriting them but Git refuses. Here's how to fix it and make Git happy.

Firstly, let's try pulling the upstream files and see what happens:

git pull upstream master

The other day I did this and got an error because of local files that had changed, with a message saying "Please, commit your changes or stash them before you can merge." Git then showed a list of the files that caused the conflict. Luckily it's easy to overwrite the local changes. Very simply, we just checkout the local files into a kind of no-man's land where you can forget about them:

git checkout -- [filename]

Do this for each file that the error message warned you about and then you can pull as usual:

git pull upstream master

Please remember that this is only for files that you're happy to overwrite, in which case it's problem solved!

That's all for now — have a great weekend.

- The DuckDuckGo Staff

2 Tweet

This blog has been archived

Thank you for reading and contributing lively discussion to our blog! Read more posts about online privacy on our new blog at spreadprivacy.com.

Interesting :)

posted by TrepanierCamille • 2 years and 1 month ago Link

For once I have it, I am glad I did not have to wait for the update

posted by oliverness • 2 years and 1 month ago Link