-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let's document: tj/git-extras #5137
Comments
@sbrl no. I had initially added the git-extras commands into #3953, but then per @waldyrious's suggestion, moved them here. |
I'm not sure this was made clear before, but might want to come to an agreement about whether to document these as top-level commands (e.g. Pinging @CleanMachine1 as a heads-up, due to this comment on Gitter. |
well to be honest, I didn't plan to do the ones which overlap, however what could be done, in the git included ones which overlap, maybe put a, see also in the desc |
To be clear, I meant overlap with other git CLI helpers (which may use the same subcommand names), not just with git itself. |
OK, what do you suggest? |
I don't think that |
yes. I feel the same way. |
Since there is no autofill with tldr, I agree that it is better to keep it similar to what the user will type for their actual command. |
How does the system prioritize them? When you execute a git subcommand which is also a git-extras subcommand, somehow the shell has to figure out which one to use. |
Why have you closed? |
@patricedenis linked this issue with #5948 and when I merged it it was closed. |
Ok, just thought we were going to discontinue support git-extras, I plan on doing more maybe tomorrow |
Yep, definitely not intended. |
Generally speaking in our case, documenting extra subcommands that are part of an addon is fine (though I recommend mentioning that they are part of an external program or something in the description), but we do not want to overwrite any pre-existing core git commands - those should be prioritised over anything provided by a third party extension. |
|
We could add it as an alias page to highlight that this command is an alias of a different page. |
Like this? #10996 |
fresh-branch is merged, but not ticked |
On it, will update it for the other open PRs too. |
Great! Missed one: #10995 |
All open PR's are merged, so we can complete this issue! 🚀 |
Maybe unpin this one since it is closed? |
We should add the commands from tj/git-extras (73):
abort
→ git-abort: add page #6243alias
→ git-alias: add page #5979archive-file
→ git-archive-file: add page #5960authors
→ git-authors: add page #5951browse
→ git-browse: add page #5959browse-ci
→ git-browse-ci: add page #8500brv
→ git-brv: add page #5966bulk
→ git-bulk: add page #8946changelog
→ git-changelog: add page #7359clear-soft
→ git-clear-soft: add page #6616clear
→ git-clear: add page #6614coauthor
→ git-coauthor: add page #6878commits-since
→ git-commits-since: add page #5968contrib
→ git-contrib: add page #6064count
→ git-count: add page #5970cp
→ git-cp: add page #5947create-branch
→ git-create-branch: add page #5982delete-branch
→ git-delete-branch: add page #6011delete-merged-branches
→ bdaada4delete-squashed-branches
→ git-delete-squashed-branches: add page #10988delete-submodule
→ git-delete-submodule: add page #8553delete-tag
→ git-delete-tag: add page #5948delta
→ git-delta: add page #6010effort
→ git-effort: add page #6002extras
→ git-extras: add page #6037feature
→ git-feature: add page #9470force-clone
→ git-force-clone: add page #8724fork
→ git-fork: add page #6013fresh-branch
→git-fresh-branch: add page #10972gh-pages
→ git-gh-pages: add page #8787graft
→ git-graft: add page #6034guilt
→ git-guilt: add page #10890ignore-io
→ git ignore: add page #3978, git-ignore: add page (and move former to git-ignore-io) #5908ignore
→ git ignore: add page #3978, git-ignore: add page (and move former to git-ignore-io) #5908info
→ git-info: add page #6058local-commits
→ git-local-commits: add page #5981lock
→ git-lock: add page #6756locked
→ git-locked: add page #7034magic
→ git-magic: add page #10889merge-into
→ git-merge-*: add page #9386merge-repo
→ git-merge-*: add page #9386missing
→ git-missing: add page #6126mr
→ git-mr: add page #7585obliterate
→ git-obliterate: add page #6099paste
→ git-paste: add page #10992pr
→ git-pr: add page #2674psykorebase
→ git-psykorebase: add page #10994pull-request
→ git-pull-request: add page #10993reauthor
→ git-reauthor: add page #6651rebase-patch
→ git-rebase-patch: add page #10995release
→ git-release: add page #6095rename-branch
→ git-rename-branch: add page #5950rename-remote
→ git-rename-remote: add page #6138rename-tag
→ git-rename-tag: add page #6092repl
→ git-repl: add page #5974reset-file
→ git-reset-file: add page #6003root
→ git-root: add page #6009rscp
→ git-rscp: add page #10996scp
→ git-scp: add page #9385sed
→ git-sed: add page #7356setup
→ git-setup: add page #6057show-merged-branches
→ git-show-merged-branches: add page #8048show-tree
→ git-show-tree: add page #6164show-unmerged-branches
→ git-show-unmerged-branches: add page #8049squash
→ git-squash: add page #7361stamp
→ git-stamp: add page #8730standup
→ git-standup: add page #7584summary
→ git-summary: add page #6065sync
→ git-sync: add page #7357touch
→ git-touch: add page #6015undo
→ git-undo: add page #5980unlock
→ git-unlock: add page #7035utimes
→ git-utimes: add page #8729The text was updated successfully, but these errors were encountered: