Open Source Friday with GitHub CLI!

GitHub Models

• GitHub Models on the GitHub Marketplace allows developers to explore and experiment with a curated selection of top models, including GPT 40 and 53 mini instruct. (1m31s)
• GitHub Models provides entitlements linked to GitHub accounts, eliminating the need for separate API keys or service sign-ups, and enabling experimentation with AI models directly within the platform, including through the GitHub CLI. (1m41s)

GitHub CLI

• The GitHub CLI tool, GH, was created to improve developer workflow by bringing GitHub functionalities into the terminal. (9m43s)
• GH can be installed in a variety of ways depending on the operating system, including Homebrew for Mac, package repositories for Red Hat and Ubuntu, and several options for Windows. (12m53s)
• The most common way to begin using GH is by running the command "ghl login," which initiates an interactive authentication flow through a web browser. (13m40s)
• A gh command provides access to a set of core commands related to issues, pull requests, and projects. (14m26s)
• The gh workflow command lists available workflows, and gh run displays recent workflow runs. (15m26s)
• The gh pr list command lists open pull requests, which can be filtered to show only those awaiting review. (18m58s)
• A command line alias, wait for me, can be created to view outstanding pull requests. (21m7s)
• The command line tool FCF can be used with the GitHub CLI to create a richer experience for viewing and checking out pull requests. (21m53s)
• The GitHub CLI has an extension ecosystem that allows for the installation and use of third-party tools, such as gh-dash. (25m25s)
• GitHub CLI users with low vision prefer using the terminal over screen reading in a web browser. (26m39s)

Challenges of GitHub CLI

• The GitHub CLI team discovered that limitations in the GitHub API, such as rate limiting and the behavior of certain endpoints, can pose challenges for users. (28m30s)
• The GitHub CLI team acknowledges the challenge of transforming a browser-first platform like GitHub into a seamless CLI experience, especially considering the wide range of user needs and the team's limited size. (30m51s)

GitHub CLI Extensions

• GitHub CLI extensions can be created by anyone to solve problems and add functionality. (33m24s)
• The GitHub team has incorporated features from community-developed extensions into the core CLI, such as the GH profile extension for managing multiple accounts. (34m11s)
• There is currently no official method for verifying the safety or trustworthiness of GitHub CLI extensions, but artifact attestation can provide information about an artifact's build process and origin. (37m8s)
• GitHub is considering ways to convey official support for extensions, potentially through the CLI, but currently, installing extensions is at the user's own risk. (38m51s)
• GitHub recognizes the importance of ensuring the security and validity of extensions, especially with the rise of AI and the use of models. (39m27s)
• The GitHub Copilot CLI extension, which became generally available in March, aims to assist developers with coding tasks in the terminal, but there are ongoing discussions about how to best leverage AI for automation use cases in this context. (42m51s)

GitHub CLI and AI

• GitHub is taking a cautious approach to integrating AI capabilities into its terminal products, prioritizing a stable user experience and responsible AI development. (44m46s)

GitHub CLI Privacy and Data Protection

• GitHub prioritizes user privacy and data protection, opting for a conservative approach by not automatically collecting terminal or operating system context unless users explicitly opt-in. (45m48s)
• The GitHub CLI emphasizes user choice, allowing users to opt-in or out of features such as telemetry and color schemes, as well as anonymized usage data collection. (47m16s)

GitHub CLI Team and Community Engagement

• The GitHub CLI team encourages community members to share their use cases and provide feedback on the CLI, including any missing features or issues encountered. (51m11s)
• The team is open to suggestions for community engagement, such as office hours, to discuss the CLI and potential contributions. (52m11s)
• Users are encouraged to explore existing CLI extensions and consider building their own, with the team welcoming feedback on how to improve the extension development experience. (53m31s)

GitHub CLI Team Members

• William, who is from Northern Ireland but currently resides in Amsterdam, has been with GitHub for over two years and has dedicated the past year to working on the GitHub CLI. (7m24s)
• Andy, based in Raleigh Durham, North Carolina, has been a part of GitHub for approximately three years. (7m47s)