tldr-pages/tldr

Let's document: fossil

Open

#6,458 opened on Sep 3, 2021

View on GitHubContributor guide
 (5 comments) (0 reactions) (0 assignees)Markdown (5,381 forks)batch import
help wantedlet's documentnew command

Repository metrics

Stars
 (63,468 stars)
PR merge metrics
 (PR metrics pending)

Description

Subcommands (https://fossil-scm.org/home/help/xxx)

  • 3-way-merge
  • add → #7108
  • addremove
  • alerts
  • all
  • amend
  • annotate
  • artifact
  • attachment
  • backoffice
  • backup
  • bisect
  • blame
  • branch
  • bundle
  • cache
  • cat
  • cgi
  • changes
  • chat
  • checkout
  • ci → #7055
  • clean
  • clone
  • close
  • co
  • commit → #7051
  • configuration
  • dbstat
  • deconstruct
  • delete → #7115
  • descendants
  • diff
  • export
  • extras
  • finfo
  • forget → #7115
  • fts-config
  • gdiff
  • git
  • grep
  • hash-policy
  • help
  • hook
  • http
  • import
  • info
  • init→ #8710
  • interwiki
  • json
  • leaves
  • login-group
  • ls
  • md5sum
  • merge
  • mv
  • new
  • open
  • patch
  • pikchr
  • praise
  • publish
  • pull
  • purge
  • push
  • rebuild
  • reconstruct
  • redo
  • remote
  • remote-url
  • rename
  • reparent
  • revert
  • rm → #7115
  • rss
  • scrub
  • search
  • server
  • settings
  • sha1sum
  • sha3sum
  • shell
  • sql
  • sqlar
  • sqlite3
  • stash
  • status
  • sync
  • tag
  • tarball
  • ticket
  • timeline
  • tls-config
  • touch
  • ui
  • undo
  • unpublished
  • unset
  • unversioned
  • update
  • user
  • uv
  • version
  • whatis
  • wiki
  • xdiff
  • zip

Contributor guide

Research direction
Review the existing fossil documentation in the tldr repository, then create missing subcommand pages following the same format.
Tech stack
None
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.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80