-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add common tasks to examples folder #7
Labels
Comments
jh3y
added a commit
that referenced
this issue
Jul 22, 2018
- no longer prepend dotfiles, leave to user definition - improve unhandled rejection error cases - overhaul README - improve overall logging to user for scenarios such as no task selected - overhaul symlinking task and provide backup option - fix issue where file already in place when attempting to symlink by removing/restoring backup
jh3y
added a commit
that referenced
this issue
Jul 22, 2018
- no longer prepend dotfiles, leave to user definition - improve unhandled rejection error cases - overhaul README - improve overall logging to user for scenarios such as no task selected - overhaul symlinking task and provide backup option - fix issue where file already in place when attempting to symlink by removing/restoring backup
jh3y
added a commit
that referenced
this issue
Jul 22, 2018
- no longer prepend dotfiles, leave to user definition - improve unhandled rejection error cases - overhaul README - improve overall logging to user for scenarios such as no task selected - overhaul symlinking task and provide backup option - fix issue where file already in place when attempting to symlink by removing/restoring backup
jh3y
added a commit
that referenced
this issue
Jul 22, 2018
- no longer prepend dotfiles, leave to user definition - improve unhandled rejection error cases - overhaul README - improve overall logging to user for scenarios such as no task selected - overhaul symlinking task and provide backup option - fix issue where file already in place when attempting to symlink by removing/restoring backup
jh3y
added a commit
that referenced
this issue
Jul 22, 2018
- no longer prepend dotfiles, leave to user definition - improve unhandled rejection error cases - overhaul README - improve overall logging to user for scenarios such as no task selected - overhaul symlinking task and provide backup option - fix issue where file already in place when attempting to symlink by removing/restoring backup
jh3y
added a commit
that referenced
this issue
Jul 22, 2018
- no longer prepend dotfiles, leave to user definition - improve unhandled rejection error cases - overhaul README - improve overall logging to user for scenarios such as no task selected - overhaul symlinking task and provide backup option - fix issue where file already in place when attempting to symlink by removing/restoring backup
jh3y
added a commit
that referenced
this issue
Jul 22, 2018
- no longer prepend dotfiles, leave to user definition - improve unhandled rejection error cases - overhaul README - improve overall logging to user for scenarios such as no task selected - overhaul symlinking task and provide backup option - fix issue where file already in place when attempting to symlink by removing/restoring backup
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue summary
Decrease the barrier for entry to use by having a folder of common example tasks;
After reading the
README
back, it doesn't feel instantly easy to pick up and use, maybe show an example task within theREADME
showing how easy it is to create a task forkody
to pick up.Also, link to personal set ups. For example; github.com/jh3y/kody_env has my personal tasks for doing various things like running shell scripts etc.
There is potential to raise awareness of
kody
and make it a go to solution for maintaining dotfiles. It has been picked up and shown on different blogging platforms but I still feel the barrier to entry may be holding it back.Expected behavior
User should feel at ease to give
kody
a spin and not think about passing it up because it's too much overhead to get started.Actual behavior
It's not super intuitive or doesn't come across as something that can be just picked up quick without major knowledge.
Steps to reproduce
Read the
README
as if you've never heard ofkody
or.files
.Resolution
Improve the
README
so thatkody
is easier to pick up and get going. Add examples into the repo so potential users can see how easy it is to get started withkody
.The text was updated successfully, but these errors were encountered: