cheat
This is the snap for cheat (based on https://github.com/cheat/cheat)
Published for with 💝 by Snapcrafters
Install
$ snap install cheat
Get testing version
$ snap install --channel=edge cheat
$ snap refresh --channel=edge cheat
Cheatsheets
Community cheatsheets come from a cheatsheet repository and are installed on first start.
These cheatsheets are read only, but can be updated calling: $ cheat.update
.
They go into:
$HOME/snap/cheat/common/.config/cheat/cheatsheets/community
Update
To update community cheatsheets call:
$ cheat.update
Personal sheets
You can create your own cheatsheets via cheat -e foo
They go into:
$HOME/snap/cheat/common/.config/cheat/cheatsheets/personal
Configuration
The config for cheat is stored here:
$HOME/snap/cheat/common/.config/cheat/conf.yml
Buildstatus
Test latest build
$ snap refresh --edge cheat
Install from store
(Don't have snapd installed?)
How to use it
See upstream README
Remaining tasks
Snapcrafters (join us)
are working to land snap install documentation and
the snapcraft.yaml
upstream so cheat can authoritatively publish future releases.
- [x] Click the green "Use this template" button above to create a new repository based on this template
- [x] Give the newly created repository a sensible name, like
godzilla-snap
if you're snapping the Godzilla software
- [x] Fork the Snapcrafters template repository to your own GitHub account.
- If you have already forked the Snapcrafter template to your account and want to create another snap, you'll need to use GitHub's Import repository feature because you can only fork a repository once.
- [x] Rename the forked Snapcrafters template repository
- [x] Update the description of the repository
- [x] Update logos and references to
cheat
- [x] Create a snap that runs in
devmode
- [x] Register the snap in the store, using the preferred upstream name
- [x] Add a screenshot to this
README.md
- [x] Publish the
devmode
snap in the Snap store edge channel
- [x] Add install instructions to this
README.md
- [x] Update snap store metadata, icons and screenshots
- [x] Convert the snap to
strict
confinement, or -classic
- confinement if it qualifies
- [x] Publish the confined snap in the Snap store beta channel
- [x] Update the install instructions in this
README.md
- [x] Post a call for testing on the Snapcraft Forum - Call for testing cheat
- [-] Make a post in the Snapcraft Forum asking for a transfer of the snap name from you to snapcrafters - [link]()
- [-] Ask a Snapcrafters admin to fork your repo into github.com/snapcrafters, and configure the repo for automatic publishing into edge on commit
- [x] Add the provided Snapcraft build badge to this
README.md
- [x] Publish the snap in the Snap store stable channel
- [x] Update the install instructions in this
README.md
- [ ] Post an announcement in the Snapcraft Forum - [link]()
- [x] Submit a pull request or patch upstream that adds snap install documentation - link
- [x] Submit a pull request or patch upstream that adds the
snapcraft.yaml
and any required assets/launchers - link
- [x] Add upstream contact information to the
README.md
- If upstream accept the PR:
- [ ] Request upstream create a Snap store account
- [ ] Contact the Snap Advocacy team to request the snap be transferred to upstream
- [ ] Ask the Snap Advocacy team to celebrate the snap - [link]()
If you have any questions, post in the Snapcraft forum.
The Snapcrafters
| Michael Berner |
| |
| Chris Allen Lane |
| |
Upstream
| Cheat |