tldr-pages/tldr

Let's document: doctl

Open

#7,475 opened on Nov 23, 2021

View on GitHubContributor guide
 (7 comments) (0 reactions) (0 assignees)Markdown (5,377 forks)batch import
good first issuehelp wantedlet's documentnew command

Repository metrics

Stars
 (63,410 stars)
PR merge metrics
 (Avg merge 7d 5h) (321 merged PRs in 30d)

Description

  • doctl
    • 1-click
    • account #7525
    • apps #7501
    • auth #7526
    • balance #7527
    • billing-history
    • completion
    • compute
    • compute-droplet #7524
    • databases #10882
      • db #10882
      • firewalls #10882
      • maintenance-window #10882
      • options #10882
      • pool #10882
      • replica #10882
      • sql-mode #10882
      • user #10882
    • help
    • invoice
    • kubernetes
      • cluster #8846
      • options #8847
    • monitoring
    • projects
    • registry
    • serverless #9318
    • version
    • vpcs

Contributor guide

Research direction
Find the missing subcommands in doctl and create tldr pages following CONTRIBUTING.md. Start with a checked item to understand format.
Tech stack
shell
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90