This post was written by our partners at Sentry—an open source error tracker that helps you prioritize, identify, reproduce, and fix issues.

Install Sentry from GitHub Marketplace or the Student Developer Pack

Sometimes bugs slip through even the most diligent of code reviews. Putting out fires can disrupt your flow, forcing you to comb through logs and user-submitted screenshots. In the meantime, your users are left with an enigmatic 500 page. To help your team get from error to fix as efficiently as possible, try Sentry—an open source project under the BSD license. Sentry alerts you to the problematic line of code, pinpoints the commit and author likely responsible, and lets you resolve the error by including fixes ISSUE_ID in your commit message.

It starts with an overlooked edge case during an otherwise routine deploy. When a new deploy introduces an error, your team gets alerted and kicks off the familiar workflow of triaging, assigning, reproducing, and, finally, fixing the error. Sentry integrates neatly into your GitHub development flow, providing you with timely information and the rest of your team with visibility into every step.

Triage

Teams with rapid release cycles are familiar with sorting through dozens of active issues to assess each error’s potential scope and severity. To speed this up, Sentry groups errors by their stack traces, highlighting the number of users impacted, frequency of error, and any custom tags—like whether the error impacts billing code—allowing engineers to prioritize the bugs with the largest potential impact.

Assign

Once you establish priority, you'll need to assign a developer with plenty of context, typically the one that introduced the error, to the issue. To narrow down the pool of potential assignees, Sentry locates the commit and the author likely responsible for the error, then suggests an owner—no need to dig through git blame to find the best person for the job. You can also link Sentry issues to GitHub issues to give non-engineering product teams visibility as your team starts resolving the issue.

Reproduce

Most errors come from unexpected user behavior and leave you asking, “How did this even happen?” Fixing these more complicated errors takes more than a stack trace. You need to understand what the user or application was doing when the error occurred. Sentry collects a breadcrumb trail of user actions leading up to an error and, when available, a snapshot of the application’s variables, browser or OS, environment, and release. With these details, you can more easily reproduce errors without needing to further inconvenience the users that experience them.

Fix

After your team fixes a bug, it’s important to track the fix as it’s deployed and resurface the issue if it doesn’t work. Similar to how you can close GitHub issues from a commit, you can mark Sentry issues as resolved using the same commit keywords with a Sentry short-id, like fixes JAVASCRIPT-E41. As the commit is deployed, Sentry will mark the issue as resolved and silence future errors coming from older releases. However, if the issue re-appears, Sentry will mark it as a regression and alert you.

Sentry is part of the GitHub Developer Program and launched their app in GitHub Marketplace last month. If you're working on an integration using the GitHub API, you're welcome to join the program as a business or an individual no matter what stage of the development process you're in.

Over 600 people made their way to London and attended our second GitHub Satellite last month. From new developers to seasoned software entrepreneurs, attendees came together for two days of discovering information, skills, and people to make their projects even better.

GitHub CEO Chris Wanstrath began the day by sharing some new developments from around the GitHub Universe—including the launch of GitHub Marketplace, a new way to find tools that improve your workflow.

Then team members from Zalando, SAP, HSBC, Bloomberg, and the Raspberry PI Foundation led sessions in "Build" and "Grow" tracks to share how how they've built tools and communities around the world. If you didn't get to hear from our Satellite speakers, the session videos are now available for you to watch on your own time.

Experience the Satellite Sessions

To see more of GitHub Satellite, watch our wrap-up video:

If you want to expand your orbit beyond Satellite, early bird tickets for GitHub Universe are on sale now. GitHub's three-day flagship conference is returning to San Francisco in October with more hands-on workshops and an after-party.

Learn more about GitHub Universe

Review requests are a great way to get the people you need to look at your work.

Now with team requests, you can find the right group of people and review code together.

Have questions about code review on GitHub? Ask away or share your comments and feedback using our help form.

The GitHub for Unity extension we announced at the Game Developers Conference last March is now open source! Download the latest release for Windows and OS X for free, and enjoy the benefits of Git and features of GitHub without leaving Unity.

Large files? No problem!

GitHub for Unity supports Git LFS, the open source Git extension for versioning large files.

Add file locking to your workflow

With the introduction of file locking in Git LFS 2.2.0, locking files to avoid merge conflicts is a simple as a few clicks. No more shouting at your colleagues from across the room (or sending them messages in ALL CAPS) telling them to leave your scene alone.

Bring the GitHub workflow to Unity

Ditch the command line and view your project history, experiment in branches, craft a commit from your changes, and push your code to GitHub—all within Unity.

Known issues and bugs

GitHub for Unity is still alpha quality. Please check out the known issues, and make sure you have backups of your work before trying it out.

Find a bug? Want to suggest a feature? Look over our Contributing Guide. We're focused on triaging reported issues as we work towards a 1.0 milestone, and we'd love your help. All contributions are welcome.

If you have any questions or comments, email us at [email protected].

Kudos

Thank you to all of the preview release participants for your feedback. And of course, our friends on the Git LFS team and at Unity.

Git LFS v2.2.0 is now available with the all new git-lfs-migrate command, making it easier than ever to start using Git LFS in your repository.

For example, if you've tried to push a large file to GitHub without LFS, you might have seen the following error:

$ git push origin master
# ...
remote: error: gh001: large files detected. you may want to try git large file storage - https://git-lfs.github.com.
remote: error: see http://git.io/iept8g for more information.
remote: error: file a.psd is 1.2 gb; this exceeds github's file size limit of 100.00 mb
to github.com:ttaylorr/demo.git
 ! [remote rejected] master -> master (pre-receive hook declined)
error: failed to push some refs to '[email protected]:ttaylorr/demo.git'

You can use the git lfs migrate info command to see which files are causing the push failure:

$ git lfs migrate info
*.psd   1.2 GB   27/27 files(s)  100%

Using the information above, you can determine which files to pluck out of your history and store in LFS:

$ git lfs migrate import --include="*.psd"
migrate: Sorting commits: ..., done
migrate: Rewriting commits: 100% (810/810), done
  master        f18bb746d44e8ea5065fc779bb1acdf3cdae7ed8 -> 35b0fe0a7bf3ae6952ec9584895a7fb6ebcd498b
migrate: Updating refs: ..., done

$ git push origin
Git LFS: (1 of 1 files) 1.2 GB / 1.2 GB
# ...
To github.com:ttaylorr/demo.git
 * [new branch]      master -> master

You can also configure the 'import' command to migrate specific filetypes, branches, and more. For a detailed overview, take a look at the man page.

This was a quick look at the migrate command available today in Git LFS v2.2.0. For more on the full release, check out the release notes.

Open source software powers the internet. Anyone using a computer uses open source, either directly or indirectly. Although it has become the industry standard, getting involved isn't always straightforward.

Because so much of the open source community works with GitHub, we're working to make it easier for people to start and contribute to open source projects. This year we've documented best practices with our Open Source Guides, released our balanced employee IP agreement which eases employee contributions, and provided insight into the state of the community with the Open Source Survey.

Now we're inviting you to join our latest effort to make it easier to contribute to the open source community: Open Source Friday.

Open Source Friday is a structured program for contributing to open source. Contribution to open source is part of our DNA with GitHub employees maintaining projects like gh-ost, Rails, Atom, Homebrew, HospitalRun and Exercism. Over the last three years, we've encouraged GitHub employees to take time at least every fourth Friday to work on open source and share what we're working on with each other. Open Source Friday has grown from this into a program anyone can take part in.

Open Source Friday isn't limited to individuals. Your team, department, or company can take part, too. Contributing to the software you already use isn't altruistic—it's an investment in the tools your company relies on. And you can always start small: spend two hours every Friday working on an open source project relevant to your business.

Whether you're an aspiring contributor or active maintainer of open source software, we help you track and share your Friday contributions. We also provide a framework for regular contribution, along with resources to help you convince your employers to join in.

Join our friends at Google, Microsoft, Facebook, Comcast, Travis CI, and thoughtbot, who believe that contributing to open source should be part of their developers' work.

Thank you @andrew, @Charlotteis, @maxcell, @benpolinsky and @stevelacy for helping us build this project! Want to help improve Open Source Friday? The app is open source, so head over to ossfriday/ossfriday to submit a pull request.

Through dozens of global partnerships, GitHub is committed to investing in communities traditionally underrepresented in tech. As part of that initiative, we're expanding our partnership with Maven, a national non-profit helping LGBTQ youth build careers in tech, and an organization we’ve worked with since 2013. GitHub is committing $100,000 over the next three years to help Maven reach more youth in the U.S., and collaborating with their team on game-changing conferences, camps, and hackathons.

Investing in queer youth events

In their own words, Maven “fosters solutions that empower queer youth to network, organize, and educate for social change”, and they’ve helped hundreds of teens go on to study tech-related fields and build careers as developers. We’ll be supporting their ambitious roadmap to reach more LGBTQ youth in tech hubs and rural areas through curriculum consultation, volunteering, and co-hosting for their three main core programs: Tech Summits, Summer Tech Camps, and the Hack 4 Queer Youth Hackathon.

• Tech Summits: These single-day conferences bring together hundreds of youth and young adults to focus on organizing in schools and build competencies in tech. Maven hosts a variety of sessions for attendees like Tech 101 workshops, Out in Tech panels, and organizing strategy brainstorms.
• Summer Tech Camps: Maven currently offers 1-2 week camp experiences for queer youth and allies in Austin, SF/Oakland, NYC, and Indianapolis. Each camp brings together 20 campers ages 14-20 for an in-depth tech career exploration. Youth will meet LGBTQ tech professionals and learn coding, marketing, and digital illustration as they build their own gaming startup.
• Hack 4 Queer Youth Hackathon: These 3-day hackathons bring together tech professionals and queer youth to build tech solutions for queer youth. Maven's 4th annual hackathon will be this fall in Chicago with around one hundred participants, and Maven will partner with oSTEM on making Hack 4 Queer Youth a part of their college national conferences.

Learn how you can support Maven's work at mymaven.org.

School may be (almost) out for summer, but we're still adding to the Student Developer Pack. Sentry is now offering error reporting to new and existing pack members—send up to 500,000 errors per month and enjoy unlimited projects and members.

Sentry provides real-time error tracking and crash reports for your web apps, mobile apps, games, and more. With Sentry, you get all the information you need to identify, reproduce, fix, and prevent bugs—from the full stack trace and the contextual details of the exception to a trail of events that led to the issue and release and commit data—so you can set priorities, triage proactively, and make sure errors don't affect your user's experience.

Sentry works with dozens of languages, frameworks, and libraries, including JavaScript, Python, Ruby, PHP, Node, Java, Go, and Swift—and it's 100% open source. Sentry also integrates with GitHub to create issues based on Sentry events.

Sign up for the pack now.

GitHub Student Developer Pack

Our Student Developer Pack gives students free access to the best developer tools from different technology companies like DigitalOcean, Datadog, Stripe, Travis CI, Sentry, and more. Oh yeah, and all students get free unlimited private repositories—perfect for summer projects.

Whether you need something to wear for a beach vacation or some heat hibernation, your shirt of the summer is here—now with more glow.

Check out the GitHub Drip Tee

With green glow-in-the-dark or bright orange font, this 90s-inspired tee is sure to help you stand out from the crowd and make summer nights a little brighter.

Head over to the GitHub Shop and grab a GitHub Drip Tee while they're still here.

先週の始め、東京で GitHub Constellation イベントが初めて開催されました。ソフトウェアに対して熱い思いを抱く 200 人の方が参加し、GitHub のエンジニア、お客様、またパートナー様による話を聞きました。参加できなかった方々に向けて、イベントのハイライトをお伝えします！

基調講演

最初に、日本のカントリーマネージャーを務める藤田純と共に GitHub の最高業務責任者である Julio Avalos がステージに上がり基調講演を行いました。Julio は、日本のマーケットに対する GitHub のコミットメントに関して繰り返し言及し、日本では毎日 18 万人以上が GitHub を利用していることを示しました。また最近の製品ローンチに関する最新情報を提供し、ソフトウェア開発ツールをすべての人が利用できるようにする、という GitHub の目標について述べました。その後、長谷部良輔氏がステージに登場し、LINE で GitHub Enterprise を利用している経験について語りました。

セッションのハイライト

Constellation の出席者は、2 つのトラックでビジネスリーダーやテクニカルリーダーから話を聞きました。テクニカルセッションでは、Ruby のコミッターでエンタープライズ向けにクラウドサービスを提供する企業 Treasure Data のソフトウェア開発者である中村浩士氏（@nahi）による、エンタープライズソフトウェア開発での OSS の捉え方に関する包括的なディスカッションも行われました。Attractor Inc. の最高技術責任者、吉羽龍太郎氏は「ビジネスでの DevOps」という話の中で、ビジネスパーソンが DevOps の取り組みにどのように関わるかについて考察しました。話の中で、絶えず変化し続ける環境に対応してビジネスの効率を高めるための手段としてDevOpsが取り上げられました。話の最後で、吉羽氏は、なぜ DevOps がソフトウェア開発者に限らずビジネスパーソンとも関係するのかを説明しました。
また、藤田純が、Yahoo! Japan、サイバーエージェント、富士通研究所のお客様をステージに招き、各企業が実施しているソフトウェア開発へのアプローチに関してディスカッションを行いました。ディスカッションの中心となったのは、ソフトウェア開発のプラクティスおよびプロセスのさらなる向上のために、組織が取り組む必要のある文化的な変化についてでした。

GitHub meetup

メインイベントの前に、GitHub コミュニティの皆様を招いて、Super Deluxe で交流イベントを開催しました。XTREME DESIGN、KDDI、Slack の各社からの講演者による啓発的な話が行われ、その後ビデオアーティストの高橋啓治郎氏 が Unity と GitHub を使ったオープンソースビジュアルアートのパフォーマンスをステージで繰り広げました。

謝辞

最後に、GitHub の日本のコミュニティ、およびスポンサーのクラスメソッド様、Constellation をご支援いただき感謝申し上げます。次回の開催を楽しみにしております。今年米国を訪れるご予定がありましたら、GitHub Universe でぜひお会いしましょう。

Mission Report: Constellation Tokyo 2017

Last week, we hosted our first ever GitHub Constellation event in Tokyo. 200 software enthusiasts joined us to hear talks from GitHub engineers, customers and partners. In case you missed it, here are some highlights!

Keynote

We started with a keynote by GitHub's Chief Business Officer, Julio Avalos, who was joined onstage by Japan Country Manager Jun Fujita. Julio reiterated GitHub's commitment to the Japanese market, and revealed that there are over 180k people using GitHub daily in Japan. He also shared updates on recent product launches, and stated GitHub's goal of making software development tools accessible to everyone. Later, Ryosuke Hasebe took the stage to share his experience using GitHub Enterprise at LINE.

Session highlights

Constellation attendees heard talks from business and technical leaders in two tracks. The technical sessions included a comprehensive discussion of how to think about OSS in enterprise software development by Hiroshi Nakamura (@nahi), Ruby committer and software developer at enterprise cloud services company Treasure Data. In his "DevOps for business" talk, Ryutaro Yoshiba, CTO of Attractor Inc., discussed how business people can get involved in DevOps efforts. His talk focused on DevOps as an effort to increase the efficiency of businesses to adapt to ever-changing environments.

Jun Fujita also lead a discussion on stage with customers from Yahoo! Japan, CyberAgent and Fujitsu Labs to explore how they each approach software development. Much focus was on the cultural changes that organizations need to undertake in order to advance software dev practices and processes.

GitHub meetup

Before the main event, we opened our doors to the GitHub community by hosting a meetup at Super Deluxe, where speakers from XTREME DESIGN, KDDI, and Slack gave lightning talks before video artist Keijiro Takahashi took the stage to show off some of the open source visual art he makes using Unity and GitHub.

Thank you

Finally, thank you to our Japanese community, and to our sponsor, ClassMethod, for supporting Constellation—we'll be back! If you plan to be in the US later this year, we'd love to see you again at GitHub Universe.

We're introducing two new tools to help maintain and grow open source communities.

Recommended community standards

As an open source project grows beyond code, it can be difficult to maintain new contributions, documentation, issues, and the legal side of running a larger project. On your community profile, you'll see a checklist showing how your project compares to our recommended community standards. From there, you can easily add any missing files.

If you're a project maintainer, view your community profile by clicking the repository header's Insights tab and selecting Community.

Easier codes of conduct

As your project grows and matures, it's often necessary to spell out community roles, norms, and expectations. One of the recommended best practices is to add a code of conduct to your project. If you click the prompt from your community profile (or begin adding a CODE_OF_CONDUCT.md file to your repository), you'll see a short list of common templates to choose from. Then you can create a pull request to add a code of conduct to your repository.

Learn more

• Community profile
• Code of conduct tool

Now you can use multiple levels of nested teams to reflect your group or company's hierarchy within your GitHub organization, making your organization's permissions structure clearer and easier to manage.

Child teams inherit their parent's access permissions, so repository permissions and @mentioning among nested teams work from top to bottom. If your team structure is Employees > Engineering > Application Engineering > Identity, granting Engineering write access to a repository means Application Engineering and Identity also get that access. And if you @mention the Identity Team or any other team at the bottom of the organization hierarchy, they're they only ones who will receive a notification.

Membership inheritance from parent to child teams isn't automatic. If you're a member of Engineering and someone creates a child team called Security, team members of Engineering aren't automatically direct team members of Security. Security and all other teams nested under the Engineering will inherit repository permissions and @mentions but nothing else.

Check out the documentation to learn more and start structuring your existing teams!

Feedback is essential to the learning process. Input from an expert at the right time can make all the difference in a software project.

In past programming classes, Professor John David N. Dionisio's printed out student assignments and commented on their code by hand, directly on the paper. Students said it was easier to understand feedback when it was in context.

When he started using GitHub’s interface to communicate with his students, he found he could introduce version control even earlier in his courses. As a result, Dionisio's students have the opportunity to use industry tools from day one of their studies.

The web app has made development more accessible sooner, letting freshmen get in on it without having to learn everything about version control. The comment threads and the ability to comment line by line tightens the feedback loop. Now printing is not really necessary because you can just look at the diffs and make comments about it.

With a streamlined process, students don't get stuck on setup

John runs his courses using GitHub Classroom to manage student assignments and Jenkins CI to deliver immediate and ongoing feedback.

Working with a live repository, he knows students will see it exactly as he does. And GitHub Classroom’s dashboard lets him share a link to the full assignment and view who has accepted it.

For students it’s easy to get started. With Classroom, I can now basically deliver a complete package, including the instructions. Instead of things being sort of scattered, and having the student accumulate it together. Documentation is there, sample code is there, and configuration files for continuous integration are there.

Every student picks it up, and if they’re off and running. They can commit, and you can look at their histories. Students have their own private repo that they would build their files on.

More substantive feedback, fewer syntax errors

Until he started using Jenkins to flag formatting issues, Dionisio had to provide his students with a flood of stylistic comments.

Now, instead of focusing on bad indentations and incorrect spacing, Dionisio can give more qualitative feedback on redundancies and best practices. His comments have evolved into more of a conversation.

I frequently give feedback in terms of design and structure, like "I would’ve instead written this line this way." And since GitHub comments are in Markdown, they're easy to read and very clear.

You can really format the code and convey your ideas. The display thread helps the student respond. It allows very context-sensitive, context-aware discussions for finer points of code.

A before and after of Dionisio's feedback—from manual markup to precise and contextual feedback using GitHub’s review process.

A few additional examples of John's feedback to students.

The goal: strong communication skills around code

In industry, developers almost never start from scratch. To be successful, they need to be able to ask questions about code, to understand what’s going on, and recognize the strategies of other developers. In the classroom, pull requests work to build those skills:

Pull requests with Markdown support are a great place to have a consistent thread of feedback. And this clear signal of, "I now accept your work"—like building a relationship of submitting your work for someone to look at, and after we workshop it for a little bit, I now accept your work.

Anything that helps me simulate tools and practices they will encounter later is always of help.

This is a post in our “Teacher Spotlight” series, where we share the different ways teachers use GitHub in their classrooms.

See more GitHub education posts

It's easy to explore code in your browser when you visit a GitHub repository, but you often want to pull that code directly into the appropriate editor and try it out. For example, if the repository contains an .xcodeproj or .xcworkspace file, you might want to open that code in Xcode.

This is possible starting today with the new "Open in Xcode" button.

The button works with Xcode 9, the latest version announced at today's WWDC, which includes GitHub integration developed by Apple. Once you authenticate into Xcode with your GitHub account, the "Open in Xcode" button will appear for relevant repositories on GitHub. Click the button and Xcode will launch, prompting you to choose a directory to clone the repository to your local machine.

Happy cloning!

The latest GitHub Enterprise release is here with updates for developers and admins alike. Customizable workflows and advanced project tracking help your team do more at every step of the development cycle.

Ready to upgrade?
Download GitHub Enterprise 2.10

Create your own tools with the new GitHub GraphQL API

The GitHub GraphQL API is now out of early access on GitHub.com and available in GitHub Enterprise 2.10. Create your own tools with greater access to data than ever before using the same API that we use to build GitHub. Ask for the exact data you need in a single request and get updates in real time—no more hitting multiple endpoints or waiting for new ones after a new enterprise feature has been released.

Check out the GitHub GraphQL API video and get started with the API today!

Find and organize repositories with topics

With Enterprise 2.10, repository admins can manually add tags to their repositories for easy search and discovery. Use topics to add relevant data and group repositories by languages used, project function, or teams responsible for maintaining the repository. Team members can use tags to filter repositories and find new ones related to their projects.

Learn more about topics

Get the full story (or no story) from your project boards

Project boards are a great way to keep your tasks organized on GitHub, and they're especially useful when working with a team. The latest enterprise release helps you accomplish more in project boards with better organization, tracking, and reviews.

When projects get complex with multiple contributors and phases, it can be difficult to keep track of what's getting done and who's doing it. Now teams can see a rich history of all activity (and the teammate behind each action) in one place with project board history.

Learn more about project board history

If your team isn't using project boards, admins can disable them by unchecking the Projects box in Settings on the repository or organization level. When they're disabled, you'll no longer see project board information in timelines or audit logs. They can be re-enabled at any time and will be restored exactly as you left them.

Learn more about disabling projects

Refine your review process

Review requests help you get the exact feedback you need from the people you need it from. Now you can use filters to find the pull requests that require your attention first. Use the Reviews filter to see the pull requests still awaiting review, unreviewed pull requests on protected branches that require a review, approved pull requests that are ready to merge, pull requests that have a review requesting changes, and pull requests that have been reviewed by a specific user.

Learn more about review request filters

Reinforce your team's code reviews by specifying who in your organization can dismiss reviews on a protected branch. In addition to the ability to leave, manage, request, and dismiss reviews, protect branches, and limit merging rights, you can ensure important feedback gets addressed. Completely remove the ability to dismiss reviews on a protected branch or restrict that ability to a subset of users or teams specified in your branch protection settings for any organization repository.

Learn more about review dismissal

Additional updates

• Git LFS 2.0.0 includes important bug fixes, an early release of File Locking, and a handful of other new improvements.
• New options give administrators the ability to configure API rate limiting from the Management Console.
• Trace changes in any part of your files over time, instead of viewing the entire file history, with improved Git blame.
• Organization owners can now limit the ability to delete repositories to themselves or members with admin permissions.
• Choose which TLS protocols to support and deprecate to fit your security policies.
• Be a part of the Early Access Program:
  • Request access to hotpatching for reduced downtime when you’re upgrading patch releases.
  • If your team is geographically-distributed, request access to geo-replication for better performance in high availability environments.

Upgrade today

Download GitHub Enterprise 2.10 to start using these features and keep improving the way your team works. You can also check out the release notes to see what else is new or enable update checks to automatically check for the latest releases of GitHub Enterprise.

Not on GitHub Enterprise yet and want to give it a try?
Request a 45-day free trial