Revise Freezer Guide for file management and restoration

[geoffreyweal]

Updated the Freezer Guide to improve clarity on file handling and added steps for tarballing and restoring data.

[gemini-code-assist]

Summary of Changes

Hello @geoffreyweal, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the Freezer Guide by providing more detailed instructions on file management, specifically focusing on tarballing for efficient handling of small files and a clearer step-by-step process for both uploading and restoring data. The updates aim to improve user understanding and streamline the interaction with the Freezer storage system.

Highlights

• Tarballing Instructions: Added a section on how to tarball files before uploading to Freezer, recommending this for collections of small files to improve upload and download efficiency.
• Step-by-Step Guidance: The guide now includes numbered steps for both uploading (tarballing and synchronizing/putting objects) and restoring data, providing a clearer workflow for users.
• Clarification on Restoring Objects: The document emphasizes the necessity of restoring data from Glacier to the STANDARD storage class before retrieval, ensuring users understand the two-stage process.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

---

In digital deep, A freezer's cold embrace waits, Data sleeps soundly.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[github-actions]

Test deployment successful!! (2026-03-10T23:54:23Z)
Preview available at https://callumwalley.github.io/mkdocs-demo-deploy/nesi/support-docs/Revise-Freezer-Guide-for-file-management-and-restoration

Seems the following pages differ;

• Freezer_Guide

See all deployed demo sites

[AgentKumara]

/gemini review

[gemini-code-assist]

Code Review

The pull request refactors the Freezer Guide documentation by introducing numbered steps for uploading and restoring objects, including a new section on tarballing files before upload and an empty section for untarballing after restore. Review feedback indicates that the untarballing section needs the actual command, the tarballing command should be updated to include gzip compression and verbose output for consistency and efficiency, and a direct support email link should be replaced with a standardized include as per the style guide.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[gemini-code-assist]

Ahoy! This be a fine addition to the guide. But a true pirate saves his space on the high seas of storage! I reckon ye should tell the landlubbers to compress their treasures. It'll save 'em space and time. Addin' a z for gzip compression and a v to see the files bein' added to the chest would be a grand idea. The other scrolls, like Other_Useful_Commands.md, speak of usin' tar -czf. Let's keep our maps consistent, eh?

Also, be sure to update the filename in the explanation below to <name of tarball>.tar.gz to match.

Suggested change

	tar -cvf <name of tarball>.tar <name of folder to tarball>
	tar -czvf <name of tarball>.tar.gz <name of folder to tarball>