Skip to content

structured the list 7_create_a_template.md#2471

Merged
chronark merged 1 commit intounkeyed:mainfrom
Chirag8023:patch-2
Oct 17, 2024
Merged

structured the list 7_create_a_template.md#2471
chronark merged 1 commit intounkeyed:mainfrom
Chirag8023:patch-2

Conversation

@Chirag8023
Copy link
Contributor

@Chirag8023 Chirag8023 commented Oct 17, 2024

before it was looking like this ( I was unable to read ):

Capture

Now it's readable 👍🏻 :

Capture2

Summary by CodeRabbit

  • New Features
    • Introduced a "Side Quest" section for creating templates using the Unkey framework.
    • Specified requirements for templates, including open source and MIT licensing.
    • Added a list of contributions with links to various GitHub repositories showcasing implementations of Unkey across different frameworks.

@changeset-bot
Copy link

changeset-bot bot commented Oct 17, 2024

⚠️ No Changeset found

Latest commit: 7988e6e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@vercel
Copy link

vercel bot commented Oct 17, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
engineering ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 17, 2024 3:12am

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Oct 17, 2024

📝 Walkthrough

Walkthrough

The pull request introduces a new section titled "Side Quest" in the oss.gg/7_create_a_template.md file. This section outlines the requirements for creating an open-source template for the Unkey framework, emphasizing MIT licensing and the inclusion of a README.md with a quickstart guide. It also lists various contributions with links to GitHub repositories showcasing different implementations of Unkey across multiple frameworks, organized chronologically.

Changes

File Change Summary
oss.gg/7_create_a_template.md - Added "Side Quest" section.
- Specified requirements for open-source and MIT licensing.
- Listed contributions with links to various GitHub repositories showcasing implementations of Unkey.

Possibly related PRs

Suggested labels

🕹️ oss.gg, :joystick: 750 points

Suggested reviewers

  • mcstepp
  • chronark
  • perkinsjr
  • MichaelUnkey

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@vercel
Copy link

vercel bot commented Oct 17, 2024

@Chirag8023 is attempting to deploy a commit to the Unkey Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions
Copy link
Contributor

github-actions bot commented Oct 17, 2024

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Here is an example:

<type>[optional scope]: <description>
fix: I fixed something for Unkey

Details:

No release type found in pull request title "structured the list 7_create_a_template.md". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (2)
oss.gg/7_create_a_template.md (2)

Line range hint 17-29: Consider standardizing the date format in the example

The instructions for adding contributions are clear and provide a consistent format. However, there's a minor inconsistency in the date format used in the example compared to the actual entries.

To improve consistency, consider updating the example date format to match the format used in the actual entries:

-» 05-April-2024 by YOUR NAME
+» 05-October-2024 by YOUR NAME

This change will ensure that the example aligns perfectly with the actual entries, providing a more accurate template for users to follow.


31-52: LGTM: Well-structured and informative contribution list

The list of contributions is well-organized, following a consistent format and maintaining chronological order. It effectively showcases the diversity of frameworks and languages supported by Unkey.

To further improve the usefulness of this list, consider adding a brief description (1-2 sentences) for each contribution. This would provide readers with a quick overview of each project's unique features or approach, making it easier for them to find relevant examples.

Example format:

» 04-October-2024 by Harsh Bhat [Flask RBAC route protection using unkey](https://github.com/harshsbhat/unkey-flask.git)
Brief description: This project demonstrates how to implement Role-Based Access Control (RBAC) in a Flask application using Unkey for API key management and route protection.
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 8b37287 and 7988e6e.

📒 Files selected for processing (1)
  • oss.gg/7_create_a_template.md (1 hunks)
🧰 Additional context used
🔇 Additional comments (2)
oss.gg/7_create_a_template.md (2)

Line range hint 1-15: LGTM: Clear and concise introduction and requirements

The "Side Quest" section provides a clear task description and well-defined requirements for creating a template. The information is consistent with the PR objectives and aligns with the overall document structure.


Line range hint 1-52: Overall assessment: Excellent improvements to document structure and content

The changes made to this file significantly enhance its readability and organization, aligning well with the PR objectives. The new "Side Quest" section provides clear instructions and requirements for contributors, while the list of contributions showcases the versatility of Unkey across various frameworks and languages.

Key strengths:

  1. Clear and concise requirements for creating templates
  2. Well-structured and chronologically ordered list of contributions
  3. Diverse range of frameworks and languages represented

Minor suggestions for further improvement:

  1. Standardize the date format in the example to match the actual entries
  2. Consider adding brief descriptions for each contribution to provide more context

Overall, these changes effectively improve the document's clarity and accessibility, making it more valuable for both contributors and readers.

@chronark chronark merged commit f54fdb3 into unkeyed:main Oct 17, 2024
Flo4604 pushed a commit to Flo4604/unkey that referenced this pull request Oct 19, 2024
github-merge-queue bot pushed a commit that referenced this pull request Oct 20, 2024
* fix: Missing plan check and ip whitelist parsing

* fix: adjust tests for ipwhitelist

* fix: Rename error code

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* fix: ipwhitelist via features vs enterprise plan

* fix: invert condition

* chore: add cache log

* fix: ensure workspace is loaded (#2470)

* chore: more logging and retries (#2475)

* Update 7_create_a_template.md (#2471)

* increase override limit

* Update create-new-override.tsx

* fix: Enhance API Key Detail Page: Change Permissions Visualization to Tree Format (#2238)

* fix:changed the permission view

* fixed issue comments

* [autofix.ci] apply automated fixes

* removed font

---------

Co-authored-by: Andreas Thomas <dev@chronark.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>

* fix: show shallow permissions followed by nested in alphabetical order (#2273)

* fix: show shallow permissions followed by nested in alphabetical order

* fix: correct the sorting of nested permissions top level keys

* [autofix.ci] apply automated fixes

---------

Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>

* Add Template to Markdown (#2362)

Co-authored-by: Andreas Thomas <dev@chronark.com>

* fix: retry on any error with disabled cache

---------

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: chronark <dev@chronark.com>
Co-authored-by: Chirag Arora <chirag8023@gmail.com>
Co-authored-by: RajuGangitla <gangitlaraju8520@gmail.com>
Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Co-authored-by: Anne Deepa Prasanna <anneraj73@gmail.com>
Co-authored-by: djnovin <95838226+djnovin@users.noreply.github.com>
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.

2 participants