Last month, we let you know of some updates to our Privacy Statement and Terms of Service and asked for help from our community. Thanks to everyone who commented and contributed feedback in our Site Policy repository, the updated Privacy Statement, Terms of Service, and Corporate Terms of Service are now in effect!
Updates to our Privacy Statement and Terms of Service are in effect as of today, May 25. You can accept them by continuing to use GitHub. Again, thank you so much to our user community for helping us improve our terms. Please let us know if you have any questions about the updates.
Today, custom domains on GitHub Pages are gaining support for HTTPS.
GitHub Pages is the best way to quickly publish beautiful websites for you and your projects. Just edit, push, and your changes are live. GitHub Pages has supported custom domains since 2009, and sites on the
*.github.io domain have supported HTTPS since 2016. Today, custom domains on GitHub Pages are gaining support for HTTPS as well, meaning over a million GitHub Pages sites will be served over HTTPS.
HTTPS (most recognizable as the lock icon in your browser’s address bar) encrypts traffic between GitHub’s servers and your browser giving you confidence that the page you asked for is the page you’re reading, from the site you think it is, and that others can’t snoop on or modify its contents along the way.
We have partnered with the certificate authority Let’s Encrypt on this project. As supporters of Let’s Encrypt’s mission to make the web more secure for everyone, we’ve officially become Silver-level sponsors of the initiative.
Action may be required on your part to secure your custom domain.
If you are using
ALIAS records for your custom domain, you’re all set and your site should be accessible over HTTPS. If it is, and your site loads correctly over HTTPS, you can optionally enforce HTTPS in your repository’s settings. Users who request your site over HTTP will be upgraded to HTTPS.
If you are using
A records, you must update your site’s DNS records with new IP addresses. Please see our guide to setting up your custom domain with Pages and update any A records you might have set.
Once your updated DNS records have propagated, and you’ve confirmed that your site loads correctly over HTTPS, you can optionally “Enforce HTTPS” for your domain in your repository’s settings, ensuring users who request your site over HTTP are upgraded to HTTPS.
These new IP addresses don’t just allow us to serve your site over HTTPS, but also places your site behind a content delivery network (CDN), allowing us to serve your site from data centers around the world at fast speeds, and offering additional protection against DDoS attacks. While the previous IP addresses will remain available for a transition period, we recommend you migrate to the new IP addresses to gain these benefits.
For almost two years you’ve been able to use saved replies to quickly respond to multiple issues and pull requests. Now saved replies have keyboard shortcuts to make them even easier to use.
To activate your saved replies press Ctrl . when composing or replying to an issue or pull request. Select the saved reply of your choice with a number, for example Ctrl 2.
Note if your saved reply ends with a
@ after inserting the saved reply it will attempt to autocomplete an issue or pull request number or username. Check out the documentation to learn more.
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!