Tab Stash

Clear your tabs, clear your mind. Only for Firefox.

Contributing to Tab Stash

For Everyone

Tab Stash has adopted the Contributor Covenant Code of Conduct. Anyone participating in the Tab Stash community, whether they are writing code, filing bugs, or simply posting questions, is asked to follow these standards.

In short, before posting please ask yourself: “If this were directed at me, how would it make me feel?” If the answer is negative, think carefully about how to re-frame your post—try to focus on specific, observable facts, avoid generalizing, and replace emotional language (“this was a huge problem”) with concrete details (“it took me an hour to recover my data because…”).

For Developers

First of all, thanks for your interest in contributing to Tab Stash! The best way to get your new feature or bugfix included is to open a pull request in GitHub. Please make sure you’ve read and followed the Code Style section below, and included adequate comments and notes in your commit message for reviewers to understand what you’re trying to do and why.

Importantly, don’t expect your pull request to be merged right away. You will likely get at least one round of constructive feedback; this is to help catch bugs and ensure the code stays maintainable for the next person who wants to contribute. I hope you will take this feedback in the spirit in which it’s given–as reflecting our shared desire to make Tab Stash the best it can possibly be.

– Josh

Getting the Source Code

Tab Stash’s source code is available on GitHub.

Building Tab Stash for Development

You’ll need a UNIX-like system (e.g. Mac or Linux) to build Tab Stash–unfortunately, building on Windows is no longer supported due to the multiple build steps involved (although patches to make the build more cross-platform are welcome). To build, you’ll need the following installed:

To build and run tests, all you have to do is run make (or make -jWHATEVER on a multi-core system):

$ make

The result will be in the dist directory. You can load it into your Firefox by following these steps:

  1. Open a new tab and go to about:debugging
  2. Click on “This Firefox” in the sidebar.
  3. Click “Load Temporary Add-on”.
  4. Browse to the dist directory, and select the manifest.json file.

An experimental port to Chrome is also built in dist-chrome.

Building Tab Stash for Release

Release builds may only be done in a clean tree with no uncommitted changes, and your HEAD commit must be pointing at a release tag (or make will create one for you with the version listed in manifest.json). In the top-level tab-stash directory, run:

$ make [-jWHATEVER] rel

All generated files in dist will be rebuilt, with debugging information and code stripped. Two package files will be generated, both of which can be uploaded to–the first,, is the actual extension. The second, tab-stash-src-X.Y.tar.gz, is the source to go along with it.

Code Style

The existing code does not always follow these guidelines consistently; if you find inconsistencies, please feel free to correct them (but please submit corrections in commits which are separate from functional changes).

Editing Icons

We recommend Inkscape. Please be sure to follow the Firefox Photon Design Guide.