Skip to content
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 .editorconfig to .gitignore #9484

Merged
merged 1 commit into from
Jul 12, 2018
Merged

Add .editorconfig to .gitignore #9484

merged 1 commit into from
Jul 12, 2018

Conversation

lucperkins
Copy link
Contributor

I find .editorconfig files to be an indispensable part of my doc-writing workflow. I'd like to be able to apply my own when working on the k8s website without imposing an editor config on others. This PR makes Git ignore any user-specific .editorconfig files.

@k8s-ci-robot k8s-ci-robot added the size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. label Jul 12, 2018
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Jul 12, 2018
@k8sio-netlify-preview-bot
Copy link
Collaborator

Deploy preview for kubernetes-io-master-staging ready!

Built with commit c1b94d4

https://deploy-preview-9484--kubernetes-io-master-staging.netlify.com

@@ -29,3 +29,6 @@ nohup.out

# Hugo output
public/

# User-specific editorconfig files
.editorconfig
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What kind of stuff would go in here? You can set your editor in your ~/.gitconfig or /git/config, which don't need to go in the repo's base directory and thus don't need to be ignored.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Check the URL in the description for more info. Editor configs are a standardized format for configuring a wide variety of editors (VS Code, Sublime, etc).

@mdlinville
Copy link
Contributor

/lgtm
/approve

Maybe you can bring up the editorconfig in a sig-docs meeting and propose the type of config we would like to try to enforce as a SIG, for people who want to use this. Maybe 80 columns and 2 spaces for a tabstop is a good place to start? I don't think we want to get too picky, and no matter what we do, we don't want to do anything that will reformat entire files when someone only wanted to edit a small thing.

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jul 12, 2018
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mistyhacks

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jul 12, 2018
@k8s-ci-robot k8s-ci-robot merged commit 5603809 into kubernetes:master Jul 12, 2018
@lucperkins
Copy link
Contributor Author

@mistyhacks Good idea, and I'll do a bit of research to see if there are any lurking downsides.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants