Skip to content

Update Readme #873

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

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update Readme #873

wants to merge 2 commits into from

Conversation

rukletsov
Copy link
Member

@rukletsov rukletsov commented Nov 28, 2024

Summary by Sourcery

Update the README to reflect the project's current state, including moving the license information higher in the document, updating the StackRox link to Red Hat, and rephrasing the alpha release warning.

Chores:

  • Move the license information higher in the document.
  • Update the StackRox link to Red Hat.
  • Rephrase the alpha release warning.

@rukletsov rukletsov requested a review from janisz November 28, 2024 13:56

If you would like to engage with the KubeLinter community, including maintainers and other users, you can join the Slack workspace [here](https://join.slack.com/t/kube-linter/shared_invite/zt-kla9qvyo-Tk~wynTSbr9EE3AjHcv4BQ).

To contribute, check out our [contributing guide](./CONTRIBUTING.md).
Copy link
Contributor

Choose a reason for hiding this comment

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

While this is somehow duplicated in the alpha release warning, I'd keep that line in the Community section.

Copy link
Member Author

Choose a reason for hiding this comment

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

Agree, that's why there is the link to the guide in the community section below : ). Unless you insist on keeping the exact wording.

Copy link
Contributor

Choose a reason for hiding this comment

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

I have no strong opinion there. The link in the rendered page is probably eye-catching enough.

Comment on lines +215 to +217
There may be breaking changes in the future to the command usage, flags, and configuration
file formats. However, we encourage you to use KubeLinter to test your environment YAML
files, see what breaks, and [contribute](./CONTRIBUTING.md).
Copy link
Contributor

Choose a reason for hiding this comment

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

Would it make sense to have a backward compatibility sub-section for that piece ?

Copy link
Member Author

Choose a reason for hiding this comment

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

Good thought. I guess at this point we don't really have clear backward compatibility guidelines nor guarantees, so maybe it's a bit too early to pull this out into a separate section? No strong opinion here, open for suggestions.

Copy link
Contributor

Choose a reason for hiding this comment

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

That was food for thought. Adding a dedicated section will also make the bottom block bigger and might make the message less catchy. Things can be left in their current state for now.

If you're interested in KubeLinter, or in any of the other cool things we do, please know that we're hiring!
Check out our [open positions](https://www.stackrox.com/job-board/). We'd love to hear from you!
KubeLinter is created with ❤️ by [StackRox](https://www.stackrox.io/) and is now powered
by [Red Hat](https://stackrox.com/).
Copy link
Contributor

Choose a reason for hiding this comment

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

The link here is wrong

Copy link
Member Author

Choose a reason for hiding this comment

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

Why? It redirects to the ACS page on Red Hat website.

Copy link
Contributor

Choose a reason for hiding this comment

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

I find it awkward to have the name of a company and the (hover) link pointing at a different address.
The current recommended corporate security practices (like phishing prevention) suggest not to click links where name and associated link address don't match.


## LICENSE
If you would like to engage with the KubeLinter community, including maintainers and other users, you can join the Slack workspace [here](https://join.slack.com/t/kube-linter/shared_invite/zt-kla9qvyo-Tk~wynTSbr9EE3AjHcv4BQ).
Copy link
Collaborator

Choose a reason for hiding this comment

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

Maybe we should remove that and keep it GitHub centric.

Copy link
Member Author

Choose a reason for hiding this comment

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

You mean not mentioning slack at all? It's a common practice, for example, trivy, falco do that.

Copy link
Collaborator

Choose a reason for hiding this comment

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

I know but who is there to answer?

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 thought you!

@rukletsov rukletsov requested a review from rhybrillou November 29, 2024 12:22
@rukletsov rukletsov requested a review from janisz November 29, 2024 12:25
@sthadka
Copy link

sthadka commented Mar 21, 2025

@sourcery-ai review

Copy link

sourcery-ai bot commented Mar 21, 2025

Reviewer's Guide by Sourcery

This pull request updates the README.md file to reflect the current state of the KubeLinter project. It updates the StackRox URL, adds Red Hat as a sponsor, and reorganizes the sections for better readability.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Updated the StackRox URL and added Red Hat as a sponsor.
  • Updated the StackRox URL from stackrox.com to stackrox.io.
  • Added that KubeLinter is now powered by Red Hat.
README.md
Reorganized the sections in the README for better readability.
  • Moved the LICENSE section higher up in the document.
  • Moved the Community section lower in the document.
  • Removed the Alpha release warning section.
README.md

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

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

Hey @rukletsov - I've reviewed your changes - here's some feedback:

Overall Comments:

  • It looks like the 'WARNING: Alpha release' section was removed - is KubeLinter no longer in Alpha?
Here's what I looked at during the review
  • 🟡 General issues: 2 issues found
  • 🟢 Security: all looks good
  • 🟢 Testing: all looks good
  • 🟢 Complexity: all looks good
  • 🟢 Documentation: all looks good

Sourcery is free for open source - if you like our reviews please consider sharing them ✨
Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.

If you're interested in KubeLinter, or in any of the other cool things we do, please know that we're hiring!
Check out our [open positions](https://www.stackrox.com/job-board/). We'd love to hear from you!
KubeLinter is created with ❤️ by [StackRox](https://www.stackrox.io/) and is now powered
by [Red Hat](https://stackrox.com/).
Copy link

Choose a reason for hiding this comment

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

issue (typo): Incorrect StackRox link.

The link to StackRox should be https://www.stackrox.io/. Also, the Red Hat link appears to be the same as the old StackRox link - is this correct?

Comment on lines +219 to +220
As a reminder, all participation in the KubeLinter community is governed by our
[code of conduct](./CODE_OF_CONDUCT.md).
Copy link

Choose a reason for hiding this comment

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

nitpick (typo): Missing period.

Add a period after the link to the Code of Conduct.

Suggested implementation:

As a reminder, all participation in the KubeLinter community is governed by our
[code of conduct](./CODE_OF_CONDUCT.md).

Insert the period at the end of the line containing the Code of Conduct link. If your file uses a specific line ending or context structure, please adjust the change accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants