Development teams often use Slack to coordinate work together on GitHub projects–ourselves included—but following all of your team’s GitHub activity in Slack channels can get difficult as teams grow. To make it easier, we’ve partnered with Slack to bring you a new GitHub and Slack app. Together, GitHub and Slack are your ultimate productivity pair, providing greater visibility into development work, right alongside your team’s conversations.
If you’re using a previous version of the GitHub and Slack app, install the new app to upgrade today.
The new Slack app brings GitHub activity right into your Slack channels to keep your teams up-to-date and productive. Subscribe to a GitHub repository from any Slack channel with slash commands (
/github subscribe owner/repo), and you’ll automatically see updates from new pull requests, issues, code reviews, and deployments.
Whenever someone on your team links to a public GitHub page, you’ll see a preview of its content for instant context. Links to pull requests, issues, comments, code snippets, repositories, and users are all supported. Support for private repositories will be available soon, so your team can share and preview links to any project you’re working on together.
The best collaboration happens in the open. Our new integration is open source and built with the same publicly-available APIs used by apps in the Slack and GitHub ecosystems. Visit the GitHub repository to contribute code, submit feature requests or bug reports, and learn more about how the app works under the hood.
There’s much more to come—we already have some big features in store for upcoming releases that will help you do more with Slack and GitHub. Soon, you’ll be able to take action on pull requests, issues, and more right from your Slack channels, making it even easier to move work forward, from conversation to commit.
Install the GitHub and Slack app today to connect your GitHub repositories to your Slack channels. If you’re new to Slack, kickstart your team’s communication with a $100 credit.
Slack is where work happens. Paired with the new GitHub app, it’s never been easier to bring together the people you need and the tools you use to do your best work.
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 <email@example.com> Co-authored-by: Matt Clark <firstname.lastname@example.org>
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.