STACKITGit/cli
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update README.md

Browse source
This commit is contained in:
Mislav Marohnić 2019-10-04 09:40:11 +02:00 • committed by GitHub
parent f596816534
commit 402e20e513
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 9 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

14
README.md
View file

@ -1,11 +1,15 @@
# Github Cli
<p align=center><i>Find the internal tool that used to live here: https://github.com/github/gh-helper-cli</i></p>
The #ce-cli team is working on a CLI tool to reduce the friction between GitHub and your local machine for people who use the command line primarily to interact with Git and GitHub. https://github.com/github/releases/issues/659
# gh - The GitHub CLI tool
The #ce-cli team is working on a publicly available CLI tool to reduce the friction between GitHub and one's local machine for people who use the command line primarily to interact with Git and GitHub. https://github.com/github/releases/issues/659
This tool is an endeavor separate from [github/hub](https://github.com/github/hub), which acts as a proxy to `git`, since our aim is to reimagine from scratch the kind of command line interface to GitHub that would serve our users' interests best.
## Process
1. For code we want to keep (production ready) create PRs and merge them into `master`. For prototype code we will merge them into the `prototype` branch because the code will most likely be garbage. We could have used one production and one prototype repo but that would have made communication more difficult and dispersed.
1. For code we want to keep (production-ready), create PRs and merge them into `master`. For prototype code, merge them into the `prototype` branch since the code will most likely be throwaway.
2. Each week we’ll have a tracking issue to coordinate plans and distribute the workload. They look like this https://github.com/github/github-cli-prototype/labels/tracking%20issue. This issue can also be used for handoff messages like this https://github.slack.com/archives/C17LP0XU3/p1569378288317500. Using issues and a project board seems like overkill right now, so start lo-fi.
2. Each week we’ll have a tracking issue to coordinate plans and distribute the workload. They look like this https://github.com/github/gh-cli/labels/tracking%20issue.
3. We zoom as a team fortnight (Tuesday)
3. We zoom as a team Tuesday fortnight