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.
Summary
Many users of the platform have lots of single author repos in GitHub, where they are the only person writing code. In these repos, Actions is often configured to run tests and catch regressions. Today, the workflow for these users entails submitting pull requests and then coming back to the site to merge and delete the branch.
We want to simplify this workflow for users and teams that make use of checks by natively allowing an option to auto-merge a pull request when all checks pass.
Intended Outcome
Increase developer productivity by allowing pull requests to be merged and closed without manual intervention.
How will it work?
We will add an option when submitting a pull request for review to auto-merge it if all checks pass and the pull request is mergeable into the target branch. A notification is also sent to the user when the pull request is closed. The user will be able to cancel this state, and revert it to a manual merge process.