Skip to content

Commit

Permalink
fix spelling issues
Browse files Browse the repository at this point in the history
  • Loading branch information
strangiato committed Jun 7, 2024
1 parent d0fadc4 commit 690cdb7
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 10 deletions.
4 changes: 3 additions & 1 deletion .wordlist-txt
Original file line number Diff line number Diff line change
Expand Up @@ -48,8 +48,8 @@ EOF
Elasticsearch
Eventing
FullAccess
GenAI
GPUs
GenAI
Gi
GitOps
HTPasswd
Expand Down Expand Up @@ -245,6 +245,7 @@ ldap
letsencrypt
libvirt
lifecycle
linter
linux
llm
machineset
Expand Down Expand Up @@ -285,6 +286,7 @@ rbac
redhat
redistributions
repo
repo's
resourceNames
rh
rhel
Expand Down
9 changes: 0 additions & 9 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,8 +27,6 @@ In short, since you are most likely a developer, **provide a ticket that you wou

We **love** pull requests! Before [forking the repo](https://help.github.com/en/github/getting-started-with-github/fork-a-repo) and [creating a pull request](https://help.github.com/en/github/collaborating-with-issues-and-pull-requests/proposing-changes-to-your-work-with-pull-requests) for non-trivial changes, it is usually best to first open an issue to discuss the changes, or discuss your intended approach for solving the problem in the comments for an existing issue.

For most contributions, after your first pull request is accepted and merged, you will be [invited to the project](https://help.github.com/en/github/setting-up-and-managing-your-github-user-account/inviting-collaborators-to-a-personal-repository) and given **push access**. :tada:

*Note: All contributions will be licensed under the project's license.*

- **Smaller is better.** Submit **one** pull request per bug fix or feature. A pull request should contain isolated changes pertaining to a single bug fix or feature implementation. **Do not** refactor or reformat code that is unrelated to your change. It is better to **submit many small pull requests** rather than a single large one. Enormous pull requests will take enormous amounts of time to review, or may be rejected altogether.
Expand All @@ -52,10 +50,3 @@ For most contributions, after your first pull request is accepted and merged, yo
- When writing comments, use properly constructed sentences

- Use spaces, not tabs.

## Coding Style

This repo includes several GitHub actions to help catch issues with coding formats, especially related to YAML formatting.

Please attempt to resolve all of the issues raised by the automatic linting when opening a PR. If you need assistance please feel free to comment on your PR to ask for recommendations.

0 comments on commit 690cdb7

Please sign in to comment.