Page MenuHomePhabricator

Add wikidata query builder to
Closed, ResolvedPublic


Project setup checklist

  • Repository:
  • Content fit
  • OS License: BSD-3-Clause License
  • Quality of strings
  • Message documentation
  • Activity
  • File format
  • Project information (see template below)
  • Commit access

Project information

Name: Wikidata Query Builder

  • Optional, SVG format recommended. Add filename in commons or

Project description:

Project page:

Project configuration (for translation admins)

Prefix: wikidata-querybuilder- (source)
Validators: None needed currently

Event Timeline

Nikerabbit added a subscriber: Ladsgroup.

@Ladsgroup Need a short description and a project page. Your patch uses the wikidata logo so I assume that is fine.

Change 640804 had a related patch set uploaded (by Nikerabbit; owner: Ladsgroup):
[translatewiki@master] Add wikidata query builder

The link is:

Text: "The Wikidata Query Builder provides a visual interface for building a simple Wikidata query. It is ideal for users with little or no experience in SPARQL, the powerful query language. "
(From T265240: intro text for expectation setting)

Nikerabbit changed the task status from Stalled to Open.Nov 19 2020, 2:28 PM

I meant something like

I'll add the short description.

Change 640804 merged by jenkins-bot:
[translatewiki@master] Add wikidata query builder

Nikerabbit triaged this task as High priority.
Nikerabbit updated the task description. (Show Details)


Error Output:
remote: error: GH006: Protected branch update failed for refs/heads/master.
remote: error: 2 of 2 required status checks are expected. At least 1 approving review is required by reviewers with write access.
 ! [remote rejected] master -> master (protected branch hook declined)
error: failed to push some refs to ''

Ah, I think I know what caused it. Will fix it right away. Sorry!

@Nikerabbit The pushes should now work again. Sorry for the trouble!

Would be nice if we could find a working mode to have these restrictions in principle, but have the user be exempt from it. Or maybe these pushes could be pull requests instead? 🤔

Pull requests are possible, but we need push access to another branch since we do not fork. As far as I know Github doesn't (always?) allow exceptions to these protection features.

No errors today. Feel free to file a new task for if you want to change the integration config.