Skip to content

NO-JIRA: chore(.editorconfig): introduce .editorconfig file for the project #809

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

Merged
merged 1 commit into from
Dec 16, 2024

Conversation

jiridanek
Copy link
Member

https://editorconfig.org/

Description

image

How Has This Been Tested?

Works on my machine (in IntelliJ, but .editorconfig is supported in all major editors).

Merge criteria:

  • The commits are squashed in a cohesive manner and have meaningful messages.
  • Testing instructions have been added in the PR body (for PRs involving changes that are not immediately obvious).
  • The developer has manually tested the changes and verified that the changes work

@jiridanek jiridanek added the tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges. label Dec 13, 2024
@openshift-ci openshift-ci bot requested review from caponetto and jstourac December 13, 2024 21:09
@jstourac
Copy link
Member

jstourac commented Dec 13, 2024

/lgtm

If I understand correctly - then e.g. for VS code, I need to install this plugin, right?

Update: yeah, based on this, looks like that https://editorconfig.org/.
Update2: should we put some note about this somewhere in our readme (not only for a newcomers) to be aware of this?

Copy link
Member Author

Choose a reason for hiding this comment

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

If I understand correctly - then e.g. for VS code, I need to install [this plugin] (https://marketplace.visualstudio.com/items?itemName=EditorConfig.EditorConfig), right?

Update: yeah, based on this, looks like that https://editorconfig.org/.

yes, that one

Copy link
Member Author

Choose a reason for hiding this comment

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

Update2: should we put some note about this somewhere in our readme (not only for a newcomers) to be aware of this?

Projects mostly don't mention this, for example vscode ohly has this comment on top of .editorconfig itself and that's that

# EditorConfig is awesome: https://EditorConfig.org

https://github.com/microsoft/vscode/blob/31092ac1a0f9e68026cd0796f184fd3dfe978069/.editorconfig#L1

Copy link
Member Author

Choose a reason for hiding this comment

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

I would not mention it either, if we mentioned everything that could be mention, nobody would ever find strength of will to read our bloated readme.

Copy link
Member

Choose a reason for hiding this comment

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

okay, I don't have strong opinion on this

Copy link
Member Author

@jiridanek jiridanek Dec 16, 2024

Choose a reason for hiding this comment

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

I wanted to also add the EditorConfig is awesome part, in order to improve our documentation (IMO it would make it more likely people open the link) but since I got lgtms already, I will merge what I have. Thanks for taking a look.

@jstourac
Copy link
Member

/override ci/prow/images

These are irrelevant for this change.

Copy link
Contributor

openshift-ci bot commented Dec 15, 2024

@jstourac: Overrode contexts on behalf of jstourac: ci/prow/images

In response to this:

/override ci/prow/images

These are irrelevant for this change.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@atheo89
Copy link
Member

atheo89 commented Dec 16, 2024

/lgtm

@jiridanek
Copy link
Member Author

/approve

Copy link
Contributor

openshift-ci bot commented Dec 16, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jiridanek

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

@jiridanek
Copy link
Member Author

/override ci/prow/images

These are irrelevant for this change.

Copy link
Contributor

openshift-ci bot commented Dec 16, 2024

@jiridanek: Overrode contexts on behalf of jiridanek: ci/prow/images

In response to this:

/override ci/prow/images

These are irrelevant for this change.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-merge-bot openshift-merge-bot bot merged commit 4332bc2 into opendatahub-io:main Dec 16, 2024
7 checks passed
jiridanek added a commit to jiridanek/notebooks that referenced this pull request Jan 8, 2025
jesuino pushed a commit to jesuino/notebooks that referenced this pull request Jun 17, 2025
…lux/component-updates/component-update-odh-workbench-jupyter-datascience-cpu-py311-ubi9-n-v2-22

Update odh-workbench-jupyter-datascience-cpu-py311-ubi9-n-v2-22 to 5435e0f
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm tide/merge-method-squash Denotes a PR that should be squashed by tide when it merges.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants