Get a more complete overview of how each of your projects is going. Now you’ll see a progress bar that tracks the to do, in progress, and done cards and visualizes the progress of each of your projects.
With this update, you can also track project boards from other repositories and organizations with more context. Enter the URL of any project on GitHub into the note field to create a project summary card—a detail card like the recently released issue summary cards. Your existing cards will update automatically, so there’s no need to manually upgrade your project boards.
Check out the documentation to learn more about tracking your project’s progress, including how to disable tracking for long-running projects and other boards you’d prefer not to track.
This month, we’re introducing a few new apps to help you write, manage, and deploy code. To see what’s new and find more ways to work better, head to GitHub Marketplace.
Testing TestQuality provides modern and powerful test plan management that’s seamlessly integrated with GitHub. Test Management workflows are extended, so you can create, update, delete, and link defects and requirements in your repository without ever leaving your testing workflows. Best of all, TestQuality is completely free for use with public repositories on GitHub.
Project management Issue.sh integrates natively with GitHub to provide agile project management with fine-grained permissions. The app includes issue boards, story points, finish time estimation, burndown charts, and more. Developers don’t have to switch contexts, and project managers can get total visibility into the development process.
Publishing Pageclip is a simple way to save form data from your website. Collect leads for your new product, set up a contact form, capture emails for a newsletter, or create white-labeled survey forms—all from your static website and without a server.
Security BackHub creates daily recurring backups of all your public and private repositories, keeping an up-to-date backup with up to three months of snapshots. Backups include the repository and all metadata including the wikis, issues, and pull requests associated with it.
Deployment Take care of your application instead of focusing on Capistrano and the asset pipeline. Cloud 66 for Rails provides everything you need to run production-ready Rails and Rack apps on any cloud and under your cloud account.
Continuous integration Cloud 66 Skycap is a container-native CI/CD solution that allows you to build your image from source code in a reliable and repeatable way by taking code from your Git repository and running your Docker build workflow step-by-step. Skycap can also produce more than one image and comes with an intuitive interface and private Docker repository.
Ready to try out these new additions? See how they can help your team work better or discover even more tools in GitHub Marketplace.
Just over a year ago Jekyll, the open source project that powers GitHub Pages, introduced shared themes. Since then, you’ve been able to use about a dozen themes to change the look and feel of your GitHub Pages site.
Starting today, you can use any of the hundreds of community-curated themes on GitHub.com. To build your site with any public, GitHub-hosted theme, add the following to your site’s
name with the repository’s owner and name.
And if you’re interested in making your Jekyll theme available to other users, simply follow the instructions for creating a Gem-based theme, and ensure the repository is public.
Working together on software is so much more than writing code. Processes like planning, analysis, design, user research, documentation, and general project decision-making all play a part in the build process. Now there’s a new way to talk through projects with your team.
Team discussions provide your team and organization members a place to share information with each other. Gone are the days of having your issues cluttered with discussions or your pull requests flooded with lengthy conversations that aren’t related to your code changes. Team discussions give those conversations a home and a URL on GitHub, so they can be shared easily across the platform or saved to reference later.
To get started with team discussions, navigate to your dashboard while logged in and choose a team from the new “Your teams” section on the right sidebar. Then click on your team to go to the discussion view. From there you can start a new discussion or join in on an existing one.
All organization members can see your discussion posts by default. Mark your post as private if you have something more sensitive to share. Only direct team members will have access to the private post and its replies.
Building on top of the nested teams functionality, notifications cascade from parent to children teams making it even easier to share important information throughout your organization.
Having trouble staying in the know about what other teams within your organization are working on? Watch a team that you’re not a member of to stay up to date on their public discussion activity. If you’re worried about getting too many notifications, that’s okay, too! You can always subscribe or unsubscribe to individual posts or decide to un-watch an entire team if the flow of information is too much.
Support for team discussions in the GitHub API v3 and v4 and GitHub Enterprise is coming soon—and stay tuned for even more features, and functionality. Our goal is to provide you with a place to organize your thoughts, discuss ideas, and work through your team’s toughest problems on GitHub.
To learn more, check out the documentation!
Whether your projects are private or public, security alerts get vital vulnerability information to the right people on your team.
Enable your dependency graph
Public repositories will automatically have your dependency graph and security alerts enabled. For private repositories, you’ll need to opt in to security alerts in your repository settings or by allowing access in the Dependency graph section of your repository’s Insights tab.
Set notification preferences
When your dependency graph is enabled, admins will receive security alerts by default. Admins can also add teams or individuals as recipients for security alerts in the dependency graph settings.
Respond to alerts
When we notify you about a potential vulnerability, we’ll highlight any dependencies that we recommend updating. If a known safe version exists, we’ll select one using machine learning and publicly available data, and include it in our suggestion.
Vulnerabilities that have CVE IDs (publicly disclosed vulnerabilities from the National Vulnerability Database) will be included in security alerts. However, not all vulnerabilities have CVE IDs—even many publicly disclosed vulnerabilities don’t have them. We’ll continue to get better at identifying vulnerabilities as our security data grows. For more help managing security issues, check out our security partners in the GitHub Marketplace.