Skip to content

WIP: Grapify all the things

Zeger-Jan van de Weg requested to merge grapify-all-the-things into master

What does this MR do?

Use the GrapeDSL, at least partially so we soon can start generate docs.

Are there points in the code the reviewer needs to double check?

Did we modify behaviour? We shouldn't do that in the current release cycle.

Why was this MR needed?

I don't want to write docs for the API if they can be generated! 😉

Does this MR meet the acceptance criteria?

  • CHANGELOG entry added
  • All builds are passing
  • Files TODO:
    • access_requests.rb
    • api.rb
    • api_guard.rb
    • award_emoji.rb
    • branches.rb
    • broadcast_messages.rb
    • builds.rb
    • commit_statuses.rb
    • commits.rb
    • deploy_keys.rb
    • deployments.rb
    • entities.rb
    • environments.rb
    • files.rb
    • groups.rb
    • helpers.rb
    • internal.rb
    • issues.rb
    • keys.rb
    • labels.rb
    • license_templates.rb
    • lint.rb
    • members.rb
    • merge_request_diffs.rb
    • merge_requests.rb
    • milestones.rb
    • namespaces.rb
    • notes.rb
    • notification_settings.rb
    • pipelines.rb
    • project_hooks.rb
    • project_snippets.rb
    • projects.rb
    • repositories.rb
    • runners.rb
    • services.rb
    • session.rb
    • settings.rb
    • sidekiq_metrics.rb
    • subscriptions.rb
    • system_hooks.rb
    • tags.rb
    • templates.rb
    • todos.rb
    • triggers.rb
    • users.rb
    • variables.rb

What are the relevant issue numbers?

Let me find those later

In case anyone cares about not writing docs for the API anymore, please just pick a file and work on it. :) /cc @tiagonbotelho @rymai

Merge request reports