Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
History is littered with hundreds of conflicts over the future of a community, group, location or business that were "resolved" when one of the parties stepped ahead and destroyed what was there. With the original point of contention destroyed, the debates would fall to the wayside. Archive Team believes that by duplicated condemned data, the conversation and debate can continue, as well as the richness and insight gained by keeping the materials. Our projects have ranged in size from a single volunteer downloading the data to a small-but-critical site, to over 100 volunteers stepping forward to acquire terabytes of user-created data to save for future generations.
The main site for Archive Team is at archiveteam.org and contains up to the date information on various projects, manifestos, plans and walkthroughs.
This collection contains the output of many Archive Team projects, both ongoing and completed. Thanks to the generous providing of disk space by the Internet Archive, multi-terabyte datasets can be made available, as well as in use by the Wayback Machine, providing a path back to lost websites and work.
Our collection has grown to the point of having sub-collections for the type of data we acquire. If you are seeking to browse the contents of these collections, the Wayback Machine is the best first stop. Otherwise, you are free to dig into the stacks to see what you may find.
The Archive Team Panic Downloads are full pulldowns of currently extant websites, meant to serve as emergency backups for needed sites that are in danger of closing, or which will be missed dearly if suddenly lost due to hard drive crashes or server failures.
A GraphQL mutation is now available for reverting a merged pull request: revertPullRequest.
Like the revert action on the pull request page in the web, calling this API creates a new pull request that reverses the changes made by the merged pull request.
GitHub Desktop 3.1.5 improves support for force pushing and fetching through the newly added Repository menu items as well as supporting pull request notifications on forks. This release also comes with many great contributions (12 changelog entries! ✨❤✨) from our open source contributors.
Force-pushing and Fetching
Previously, a user could only force push after an action such as rebasing. Now, when users find their branch in any diverged state, they can opt to use the force push Repository menu item. For example, a user can force push when commits exist on the remote that they are sure they want to overwrite.
Similarly, a user may find themselves in a new local branch they are not ready to publish, yet they want to fetch to see if there are any new changes on their main branch they would want to merge in. Instead of having to switch branches, they can use the Repository menu item to fetch those changes.
Notifications for Forks
If you have been enjoying our Pull Request notifications on your repositories, you will be happy to hear that with 3.1.5 those same notifications are supported on forks.
Open Source Contributions
We love the help we get from the open source community, providing many fixes and improvements for everyone to enjoy.
Thank you @angusdev for contributing all these fixes:
Hide window instead of hiding the app on macOS
The repository change indicator is visible if repository list item is selected and in focus
Tooltips are positioned properly if mouse is not moved
Tooltips of long commit author emails wrap to multiple lines
Clone repository progress bar no longer hidden by repository list
Close repository list after creating or adding repositories
Thank you @tsvetilian-ty for adding support for JetBrains Toolbox and JetBrains Fleet editor for Windows.
Thank you @zipperer for adding support for emacs editor.
Thank you @patinthehat for adding support for JetBrains PhpStorm and WebStorm editors
Thank you @daniel-ciaglia for adding support for VSCodium as an external editor.
Thank you @Shivareddy-Aluri for adding the ability to copy tag names from the commit list.
Thank you @j-f1 for improving the the diff view by adding highlighting to Arduino's .ino files as C++ source.