Sadly, GDC 2018 is coming to a close. Tens of thousands of developers visited San Francisco to explore the latest and greatest in the gaming industry—including a large number of Unity developers who might be excited to hear that we’ve released GitHub for Unity Beta to support them through their adventures in game development.
Our Unity package provides Unity game developers with the benefits of source control and GitHub without having to switch to the command line. The package already included basic Git support from within Unity and allowed you to use GitHub features in just a few clicks. With our latest update, you can now take advantage of Git LFS and file locking, too.
Git-LFS provides a unique experience for game developers. With the ability to store your large asset files outside your repository (but still on GitHub.com servers) your repository becomes a more manageable size, making cloning and fetching much faster. You gain versioning and the same integrated Git workflow you use for text files for large asset files. Git-LFS also brings your team file locking, ensuring your assets are not overwritten or corrupted.
And don’t forget, our package is open source. We encourage you to share feedback, report bugs, and contribute where you can! Just visit our GitHub for Unity repository to get started!
As your projects grow in size and complexity, it can be challenging to make sure all of the code changes are reviewed by enough people on your team. Now, with the a multiple reviewer requirement, you can specify exactly how many people are required to review every pull request—so important projects are protected from unwanted changes.
To require multiple reviewers for pull requests, go to your repository’s settings and select “Branches”. Under “Protected branches”, select the branch you’d like to protect with a multiple reviewers requirement. There you can select the number of reviewers required for each pull request to that branch.
After you’ve selected the number of reviewers, you’ll see that number and the status of their reviews in the sidebar and merge section of pull requests to protected branches.
Whether you’re working on open source projects or collaborating with new developers on your team, it’s not always clear who you’re working with and how they’re connected to the project you’re working on.
With hovercards, you can hover your mouse over a contributor’s avatar—or most places you see their username—to get more information about who you’re collaborating with. On every hovercard, you’ll see a larger avatar image and profile information, so be sure to check if your profile is up to date with what you want others to see on your hovercard.
You’ll also see information about the individual that’s specific to your interaction with them, like which teams they belong to in your organization, if they are a code owner, if they’re contributing to their very first pull request, and more.
REST API and GraphQL API support are currently in preview—and stay tuned for hovercards in a GitHub Enterprise release soon.
A new version of Git LFS, the open source Git extension for versioning large files, is now available. Git LFS v2.4.0 comes with a rewrite of the underlying pattern matching engine, an enhanced API, standardized progress meter formatting, bug fixes, and more.
With v2.4.0, you’ll get a complete reimplementation of the engine that decides which files do and don’t match commands that accept
--exclude flags. That means Git LFS has gained support for character ranges and classes. It’s also a step toward standardizing the meaning of certain patterns—stay tuned for more advanced pattern matching in future LFS releases.
Many of the progress meters that have appeared throughout Git LFS are now unified into a single implementation, which matches Git’s style:
~/example (master) $ git lfs prune prune: 13 local object(s), 3 retained" prune.log prune: Deleting objects: 80% (8/10), done" prune.log
The progress meter you see when sending or receiving Git LFS objects is also clearer and more focused. You’ll now see a moving average rate for the transfer—and you’ll no longer see a count of “skipped” objects:
~/Desktop $ git lfs clone email@example.com:ttaylorr/example.git Cloning into 'example'... # ... Downloading LFS objects: 40% (55/136), 96 MB | 15 MB/s
Git LFS now includes any affected references in API requests. This change is a first step toward allowing contributions from owners in pull requests using Git LFS.
You’ll also see a handful of other new features and bug fixes in v2.4.0 like
git lfs ls-files, new flags in
git lfs migrate, more Linux support, and cleaned-up package internals.
And thanks to the great work of the Git LFS open source community, you’ll find support for NTLM SSPI authentication on Windows, fixes for memory alignment issues on 32-bit architectures, and more.