[Feature Request] Add "Compress" / "Archive" action to complement "Uncompress"

Closed
  • Is something wrong?
#49 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@prismatic7 is already working on this.

Since Oct 23, 2026.

  • #79 by @prismatic7 — open

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
macos, swift
Domain
desktop

Research direction

Start from the existing Uncompress action in the file operations list and trace how it is registered, configured and executed, then mirror that structure for a Compress action. The issue leaves open the default format, destination and naming scheme, so confirm those with maintainers before writing code. Done means a Compress action appears beside Uncompress and produces a .zip (optionally .tar.gz) that the user can configure.

Written by the indexing model from the issue text.

Description

Feature Description

Currently, Forel includes an Uncompress action in the file operations list, but there is no corresponding Compress (or archive) action available. Adding a compression action would allow automating workflows that package files or folders (e.g. creating .zip or .tar.gz archives).

Proposed Solution

Add a Compress action under the standard file management section (alongside Move to folder, Copy to folder, Rename, and Uncompress).

Useful configuration options for this action:

  • Format: Standard archive formats (at least .zip, optionally .tar.gz).
  • Destination: Option to place the archive in the current directory or specify a target path.
  • Archive Name: Custom naming scheme or inherit from the source file/folder and/or Timestamp.
  • Cleanup (optional): Toggle to delete the source files after successful compression.
Context / Use Case

Automating file organization often involves both extracting incoming archives and bundling processed files into archives before moving them to long-term storage or cloud destinations.

Screenshot
Image
Dominant language
Swift
Stars
757
Forks
23
Avg merge
1d 20h
Merged PRs (30d)
11

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from lab421/forel

All issues in lab421/forel

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.