mathiasbynens / mathiasbynens/dotfiles

.extra resources ideas

Open
#522 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
31.5k
Forks
8.4k
PR merge metrics
No merged PRs in 30d

Description

A few ideas that may or may not fit into this project:

  1. Adding popular .extra setups to the README? It may be beneficial for people to see how others are customising this setup in an extensible way.
  2. Adding an option to the bootstrap.sh to bootstrap with a given .extra repo url. While maintaining my own extras-toolbelt, it would be nice to run bootstrap.sh, and it prompt for a link to clone a .extra file before sourcing happens, or something fully automated for users that do like the .extra approach.

I could also see where both of these aren't solving that big of a problem, but I wanted to see what some of you thought.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Read the README and bootstrap.sh to understand how .extra files are currently documented, cloned, and sourced. The issue contains two possible changes rather than a settled scope; done would require an agreed direction and a defined README update or bootstrap.sh behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
shell
Domain
cli, documentation
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.