COLLECTED BY

Organization: Archive Team

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.

Collection: ArchiveBot: The Archive Team Crowdsourced Crawler

ArchiveBot is an IRC bot designed to automate the archival of smaller websites (e.g. up to a few hundred thousand URLs). You give it a URL to start at, and it grabs all content under that URL, records it in a WARC, and then uploads that WARC to ArchiveTeam servers for eventual injection into the Internet Archive (or other archive sites).

To use ArchiveBot, drop by #archivebot on EFNet. To interact with ArchiveBot, you issue commands by typing it into the channel. Note you will need channel operator permissions in order to issue archiving jobs. The dashboard shows the sites being downloaded currently.

There is a dashboard running for the archivebot process at http://www.archivebot.com.

ArchiveBot's source code can be found at https://github.com/ArchiveTeam/ArchiveBot.

TIMESTAMPS

GitLab Workflow

The GitLab Workflow extension integrates GitLab into Visual Studio Code.

If you face an issue, check out our troubleshooting page and if it's not listed, please report it.

Minimum supported version

GitLab versions 16.1 and later. While many extension features might work with earlier versions, they are unsupported.
GitLab Duo Code Suggestions requires both:
1. GitLab version 16.8 or later.
2. VS Code 1.92.2 or later.
Security Findings requires GitLab Workflow version 3.74.0 or later, and GitLab Ultimate.

To find your GitLab version, visit /help (like https://gitlab.com/help).

Features

After you set up the extension, this extension adds GitLab features to your preferred IDE:

Manage projects and code

Manage issues and merge requests

View GitLab issues and merge requests. View issues, comments, merge requests, and changed files in the VS Code sidebar.
Build custom, saved searches to meet your needs.
Create and review merge requests.

Manage CI/CD pipelines

Manage your pipelines. View your pipeline status and open the related merge request. Use advanced pipeline actions to create, retry, or cancel a pipeline.
View CI/CD job output. View the output of a running or finished job in an editor tab.
Test your GitLab CI/CD configuration locally.
Auto-complete GitLab CI/CD variables in your .gitlab-ci.yml pipeline file.

AI-assisted features

GitLab Duo Chat: Interact with an AI assistant directly in VS Code.
GitLab Duo Code Suggestions: Suggest completions to your current line of code, or write natural-language code comments to get more substantive suggestions.

Other features

View security findings in your current branch
Manage snippets. Create and insert snippets, and create snippet patches.

Setup

This extension requires you to create a GitLab personal access token, and assign it to the extension:

Install the extension from the Visual Studio Marketplace and enable it. If you use an unofficial version of VS Code, install the extension from the Open VSX Registry.
To sign in to your GitLab instance, run the command GitLab: Authenticate.
1. Open Visual Studio Code, then open the command palette by pressing Command + Shift + P.
2. In the command palette, search for GitLab: Authenticate and press Enter.
3. Select your GitLab instance URL from the offered options, or enter one manually.
  - When manually adding an instance to URL to GitLab instance, paste the full URL to your GitLab instance, including the http:// or https://. Press Enter to confirm.
4. For GitLab.com, you can use the OAuth authentication method.
5. If you don't use OAuth, use a Personal Access Token to log in.
  - If you have an existing personal access token with api scope, select Enter an existing token to enter it.
  - If you don't, select Create a token first, and the extension opens the PAT settings page for you. If this method fails, follow the instructions in the GitLab documentation.
6. Copy the token. For security reasons, this value is never displayed again, so you must copy this value now.
7. Paste in your GitLab personal access token and press Enter. The token is not displayed, nor is it accessible to others.

The extension automatically matches your Git repository remote URL with the GitLab instance URL you specified for your token. If you have multiple accounts or projects, you can choose the one you want to use. For more information, see Switch GitLab accounts in VS Code.

The extension is ready to use. If your project has a pipeline for the last commit, and a merge request from your current branch, information about both is displayed in the Visual Studio Code status bar.

Commands and extension settings

For a full list of GitLab commands you can run from the VS Code Command Palette, see:

Browse a repository without cloning

See Browse a repository in read-only mode in the GitLab documentation.

Roadmap

To learn more about this project's team, processes, and plans, see the Create:Editor Extensions Group page in the GitLab handbook.

For a list of all open issues in this project, see the issues page for this project.

Contribution

This extension is open source and hosted on GitLab. Contributions are more than welcome. Feel free to fork and add new features or submit bug reports. See CONTRIBUTING for more information.

A list of the great people who contributed this project, and made it even more awesome, is available. Thank you all! 🎉

Apr	MAY	Jun
	19
2024	2025	2026