API Research

Commit to adventure with the Questocat tee

Inspire your inner adventurer with our fearless Questocat by your side. From merging old pull requests to exploring new lands, you’ll always be ready to commit to adventure—just look at the back of your shirt if you need a reminder. This vintage game-inspired design is available now in the GitHub Shop.

Get your Questocat tee

github-questocat-2017

Adventure over to the GitHub Shop to get one before they’re gone. And pick up a Piratocat or Social Coding shirt for just $17.50 as part of our Closeout Sale while you’re there!

We shot all Questocat photos at Brewcade SF. Check out upcoming Brewcade events.

Quickly review changed methods and functions in your pull requests

The biggest barrier to code review is often time, but there’s a new way to easily understand how changes impact your code. Now you can navigate to changed methods and functions right from your pull request file finder.

Changed methods and functions

Searching the file finder for a method or function in a Go, JavaScript, Ruby, or TypeScript file will provide you with a timeline-style view of the results, so you can skip to the most impactful parts of a pull request. Check out the documentation to learn more.

We hope this helps make your review process even more efficient. Let us know if you have any feedback—or if there are other search functions you’d find useful using our help form.

APIMatic SDKs Now Support OAuth 2.0

APIMatic, a developer experience platform that generates SDKs, announced the SDKs generated through its platform will now support OAuth 2.0. Prior to this announcement, OAuth 2.0 support within APIMatic was limited to authentication token headers within requests. APIMatic mentioned that full OAuth 2.0 support has been on the roadmap for quite some time as it is quickly becoming the best practice for authorizing shared user data, especially among API providers.

Webcast recap: What data science can learn from open source development

data_science

Last week, Solutions Engineering Manager Aziz Shamim sat down with Datascope Analytics’ Jess Freaner to talk about how data scientists are uniquely positioned to adopt best practices from both science and software—and how her team is using open source practices to enhance collaboration and results. In case you missed it, here’s a recording of the webcast, along with a few of our takeaways.

Watch the webcast

Highlights

Transparency and openness are essential to Datascope’s success.

Feedback and collaborative knowledge-sharing are hallmarks of successful open source projects. Similarly, transparency and constant communication with clients is key to the success in data science according to Jess. Other practices that cross over from open source include frequent check-ins and reviews, shared documentation, and “reference code” that keeps the Datascope Team and clients on the same page.

Data scientists can benefit directly from open source.

At Datascope, teams contribute regularly to open source projects. They also maintain and develop projects of the own, including Textract, a library that extracts text from difficult documents to work with, such as PDFs, and traces, “a library for dealing with unevenly spaced time series that’s quite handy when efficiently working with sensor data.” Building on the knowledge shared by industry peers, Datascope can move their open projects beyond what could they could have accomplished in a vacuum.

Data scientists can start using open source practices today.

Jess and Aziz also shared four key areas of focus for teams wanting to get started with open source. In short, open source can help teams be more iterative, modular, hypothesis-driven, and human-centered. Integrating these concepts into your data science practice can help your team solve problems in a more holistic, collaborative, and agile way.

Hear more from Jess and Aziz in our webcast recording.

Making it easier to grow communities on GitHub

Open source is all about building communities around shared challenges. Thanks to some subtle (and not so subtle) improvements in the past few months, it’s now easier to make your first contribution, launch a new project, or grow your community on GitHub:

Contributor badges

One of the best ways to grow your community is to welcome new contributors. To make it easier to identify when a user is new to your project, maintainers now see a “first-time contributor” badge when reviewing pull requests from users that have not previously contributed to the project.

screen shot 2017-07-24 at 3 14 45 pm

Once the pull request is merged, you will see a “contributor” badge on the user’s comments. In addition to being a badge of pride for contributors, the additional flag can also help maintainers better separate signal from noise in lengthy or heated discussions. This information is also exposed via the GraphQL API as the issue, pull request, or comment’s authorAssociation.

Easier open source licensing

You’ve been able to select an open source license template for a while. Now, when you click the “add a license” button from your community profile, or begin adding a LICENSE file via the web editor, you’ll be presented with a new license picker:

Open source license picker

The license picker offers a brief overview of the license as well as the full text, and allows you to customize any applicable fields before committing the file or opening a pull request.

Simpler email privacy

Joining a community and making your first contribution can be intimidating. For one, not everyone wants their personal information to be public, often inadvertently the default workflow for many Git online tutorials.

While you’ve been able to hide your email while performing web-based commits for a number of years, and block pushes that expose your email address more recently, now, when you check the “keep your email address private” option in your email settings, we’ll also prevent your email from displaying in places like on your profile, in search results, or via the API so that you can contribute more confidently.

email privacy settings

We’ve also made “keep my email private” the default for new users going forward, and regardless of your email privacy settings, your email address will never be visible to logged out users.

Better blocking

Not every open source interaction is a positive one. If you navigate to a repository and someone you’ve blocked is a prior contributor, we’ll show you a warning so that you can make an informed decision if you’d like to contribute to the project or not:

blocked prior contributor warning

In addition to repositories you own, blocked users are now no longer able to comment on issues or pull requests you author in repositories owned by organizations or other users.

We hope these improvements will help you make your first contribution, start a new project, or grow your community. If you have any questions, check out the building a strong community documentation or get in touch.

Google Releases Final Android O Developer Preview

Google today made what it calls the “final preview” of Android O available to application developers. This new build carries with it all the bits and pieces developers need to make their apps fully Android O capable.

The Rise of AI Is Forcing Google and Microsoft to Become Chipmakers

By now our future is clear: We are to be cared for, entertained, and monetized by artificial intelligence.