Organizing issues and pull requests with labels can help you manage the chaos and be more productive. To support your labeling efforts and make labels even more useful, we’ve made a few enhancements.
When words are just not enough, include emoji in your labels to express yourself and the needs of your project through tiny images.
Add descriptions to your labels to provide even more context and help your contributors apply the right ones to their issues or pull requests. Descriptions will appear when you hover your mouse over labels around GitHub.
Now that labels include descriptions, we’ve added search to the “Labels” page of each repository to help you find the one you’re looking for. Filtering labels in the sidebar of your issue or pull request also filters by description.
When editing a label, you’ll now see a preview of how it will appear once you save it. Use this preview to choose the perfect color or see how your emoji look.
API and Enterprise support for these features is coming soon!
With faster onboarding for junior developers, increased code quality, and more thorough code review, it’s easy to see why more developers than ever are writing code collaboratively. Your team’s (and our own) great results from social coding motivated us to popularize the pull request—and more recently—bring real-time collaboration to your text editor with Teletype for Atom. Today, we’re building on these tools with support for multiple commit authors.
Commit co-authors makes it easy to see who has contributed to every commit, regardless of how many contributors there are—and every author gets attribution in the pull request and in their contribution graph.
To add co-authors to a commit, just add one or more “Co-authored-by” trailers to the end of the commit message:
Commit message Co-authored-by: Joel Califa <firstname.lastname@example.org> Co-authored-by: Matt Clark <email@example.com>
Include your trailers at the end of your commit message, and have at least one line of white space before them.
Try co-authors out today anywhere on the GitHub platform, including GitHub Desktop.
Issue and pull request templates help teams gather the right information from the beginning of a thread, but sometimes one template just isn’t enough. Now project maintainers can have and use multiple templates in their repositories.
To add multiple issue templates to a repository create an
ISSUE_TEMPLATE/ directory in your project root. Within that
ISSUE_TEMPLATE/ directory you can create as many issue templates as you need, for example
ISSUE_TEMPLATE/bugs.md. To use those issue templates add
?template= and your template name to the new issue URL. Continuing the example, if you create the template
bugs.md you add
?template=bugs.md to the new issue URL, so it becomes
ISSUE_TEMPLATE.md files will continue to work as the default when a template isn’t specified in the new issue URL. Pull request templates follow the same pattern: add a directory called
PULL_REQUEST_TEMPLATE to the root directory of your repository, and add the
?template= to your pull request URLs. And if you’re worried about extra clutter in the root directory of your project, all of these directories work within the
.github folder as well
To read more or learn about additional options, check out the documentation.
Repository owners, collaborators, and prior contributors to a public repository can now more easily report comments, issues, pull requests, and commit comments to GitHub Support.
Selecting the icon above will open a new contact form where you can provide more information and additional screenshots. You can also let us know whether it’s a spammy, harmful, or off-topic comment.
Comment authors also have the ability to report their own comments if another person has edited their comment in an abusive manner.
Check out the documentation to learn more about reporting comments.
This month, we’re introducing two new apps to help you monitor your APIs and improve productivity by measuring team dynamics. Head over to GitHub Marketplace to discover new tools for building better software.
REST API monitoring
Moesif provides real-time visibility into your live API traffic with advanced analytics so you never miss a beat. Analyze customer usage on your API and deeply understand every error, and prevent minor issues from becoming major outages through passive monitoring of your live API traffic. You can even recieve automatic alerts to API problems with integrations for Slack and PagerDuty.
Measuring team dynamics
DeepAffects is an emotional analytics application for managers and team leads to get issue-level insights that improve team dynamics and productivity. DeepAffects analyzes emotional queues and tones in issue descriptions and comments to help identify high-resolution time issues or disagreements within teams. Monitor and measure happiness, trust, and conflicts among team members to determine overall impact on projects. DeepAffects provides you with information that can help you build and organize higher performing teams.
Ready to try out these new additions? See how they can help your team work better or discover even more tools in GitHub Marketplace.