-
Notifications
You must be signed in to change notification settings - Fork 817
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding option for updating community cheats #552
Comments
Maybe not just the community cheatsheets but all version controlled cheatpaths. I have my personal cheatsheets also in a git repository. Maybe a configuration option for |
Hi, @bernermic 👋
Excellent! Thanks again, as always, for your work. 🎉
Yeah, this has been on my mind too. I haven't given this a lot of thought, but here's something of an unstructured "brain dump" on the topic:
I haven't come to any conclusions yet. The above is where my mind is currently, though. Feel free to share any input you may have. Thanks. |
Hey @chrisallenlane , I did not think of the conflicting part. So doing the update in a script should be good enough😀 Greetings |
Not sure if this should be its own issue or if it fits in here, but: I'd also really like an auto upload feature for personal cheatsheets as well. Something where I can About the implementation:
For option 2 to be really nicely extensible you'd have to expose some information to the called hook, such as the path to the edited cheatsheet, maybe the directory it's contained in for ease of use and so on. I guess exposing this either via parameters to the hook or via environment variables would be nice. You could then also provide a "on-start" or "once-a-day" hook or something where the community repo could be updated right after the cheat exe is started. |
@bernermic has taken a first pass at implementing this with #617. |
If I may give my two cents and suggest an alternative way of doing things, if a flag were to be implemented where one could refer to a given cheatpath by its name (e.g.: This would allow the user to decide when to commit, push or pull, as well as include more insightful commit messages, without having to go to the directory of that given cheatpath.
|
Bit of a note-to-self here: I'm currently re-writing all of the project documentation. I have temporarily removed @bernermic update script information from the |
The more I think about this, the more essential I realize this is. I also think I was too timid previously. It's probably not all that hard to:
If the branch is dirty, I can just fail out with an error message telling the user to clean it up. As long as I don't attempt to sort out any of the conflicts within Anyone reading this is welcome to share feedback on this approach. Unless someone has a convincing argument as to why this is a bad idea, I'll probably take a crack at implementing it in the near-term. |
Hey @chrisallenlane,
working on the snap version is finished now :) I will do some final tests and release it to the public channel soon.
While working on the snap I had an idea I want to share.
Describe the solution you'd like
Cheat clones the community cheatsheets on initialization now. It would be cool to have an option to update this to the latest version via cheat cli.
Additional context
Something in the lines of
cheat -update
which updates all community based cheatsheets.The text was updated successfully, but these errors were encountered: