Skip to content

Conversation

@BA-CalderonMorales
Copy link

Simply structuring this a little nicer so that it's not screaming like AI helped generate the root readme.

Love what you guys are doing with providing the information to the world for free. Want to do my part wherever possible to help convey the message to others around the globe more easily.

  • Added details and summaries for various sections in README.
  • Provides faster way to get to important information
  • Sets up structure for easier updates to key sections
  • Allows maintainers to add more details to environment setup for easier replication.

Also recommend adding:

  • PR Template
  • CODEOWNERS
  • .devcontainer (for people to leverage github codespaces)

Please feel free to reach out if you ever need a PR review for anything related to automation. Would love to help make this something for others to leverage.

Cheers!

- Added details and summaries for various sections in README.
- Provides faster way to get to important information
- Sets up structure for easier updates to key sections
- Allows maintainers to add more details to environment setup for easier replication.
@BA-CalderonMorales
Copy link
Author

Feel free to disregard if you'd like to keep the current structure, but there are smells to codebases now that don't "care" about code quality. It usually starts with seeing if you're docs have a ton of emojis in it.

Something to easily prevent by updating the instructions for your ai cli tool of choice (CLAUDE.md, copilot-instructions.md, GEMINI.md, AGENTS.md, etc.) to include a rule to avoid adding emojis to anything when pushing out code to your github repos.

I've set this up for some of my projects and it's relatively simple.

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.

1 participant