https://github.com/jim/briefcase

Makes it easier to keep dotfiles in git
https://github.com/jim/briefcase

Last synced: about 1 year ago
JSON representation

Makes it easier to keep dotfiles in git

• Host: GitHub
• URL: https://github.com/jim/briefcase
• Owner: jim
• License: mit
• Created: 2010-11-02T08:22:47.000Z (over 15 years ago)
• Default Branch: master
• Last Pushed: 2012-04-14T15:56:47.000Z (over 14 years ago)
• Last Synced: 2025-05-25T21:07:29.948Z (about 1 year ago)
• Language: Ruby
• Homepage:
• Size: 271 KB
• Stars: 43
• Watchers: 3
• Forks: 2
• Open Issues: 3
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# Briefcase

[Briefcase](http://jim.github.com/briefcase/) is a tool to facilitate keeping dotfiles in git, including those with private information (such as .gitconfig).

By keeping your configuration files in a git public git repository, you can share your settings with others. Any secret information is kept in a single file outside the repository (it’s up to you to backup and transport this file).

[The project homepage](http://jim.github.com/briefcase/) includes

installation and usage documentation.

[![Build Status](https://secure.travis-ci.org/jim/briefcase.png)](http://travis-ci.org/jim/briefcase)

## Changelog

* 0.4.2 Git command argument are properly escaped (Sebastian Spieszko)

        Changed the instruction delimiter when redacting files to '!!'.

* 0.4.1 Git command now properly passes options through to git, and also allows

        git output to display in color.

        Path environment variables inherit settings for parent directories.

* 0.4.0 Renamed project to Briefcase. First public release.

* 0.3.0 Added code documentation, internal renaming, general cleanup. First public release.

* 0.2.0 Added redact command, use .redacted for dynamic dotfiles

* 0.1.3 The sync command no longer creates symlinks for dynamic files

* 0.1.2 Added dynamic file generation

## Note on Patches/Pull Requests

* Fork the project.

* Make your feature addition or bug fix on a topic branch.

* Add tests for it. This is important so I don't break it in a future version unintentionally.

* Commit, do not mess with rakefile, version, or history.

  (if you want to have your own version, that is fine but bump version in a commit by itself I can ignore when I pull)

* Send me a pull request.

## Copyright

Copyright (c) 2012 Jim Benton. See LICENSE for details.