-
Notifications
You must be signed in to change notification settings - Fork 76
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
Document consistency goods with files examples #129
Comments
@arthurvr is this something you could help with? A list of repos with config files in use, highlighting the (in)consistencies would be useful. Some more files to add to the list: On the dev leads meeting the idea was brought up to edit these files in one repo, then use bower/npmcopy to add/update them in individual repos. That would still require commits to each repo, but might still make it quite a bit easier to mange. Using bower/npmcopy, each repo can decide which files to actually include, so a project without CSS won't need to have a Regarding |
Note from @arthurvr from on qunitjs/api.qunitjs.com#115: The package.json there uses 2 spaces for indent. That applies to other repos as well, since we use |
Regarding the centrally managed repo: If we have that, we could also include those files in this repo, to show the "current" config files on contribute.jquery.org, via @partial: https://github.com/jquery/grunt-jquery-content#partial |
There haven't been any objections, so I think we're good to move forward on this. Is anyone interested in leading this? |
I created a repo on the jquery-support org for this: https://github.com/jquery-support/dotfiles Would be great if someone could do the initial collection of the various config files. I can help with getting them published and integrated elsewhere. |
After a discussion on qunitjs/api.qunitjs.com#114 (comment), it sounds we might use some examples of our kickstart configuration files we already use on most projects.
That might include, not exclusively:
.editorconfig
As the style guides, these might be strongly enforced, but breaking some rules - to explore to new standards - are welcome.
The text was updated successfully, but these errors were encountered: