search

dev-AshishRanjan / Idea-Arca

Idea Arca (Latin: "Idea Vault") is a Project Idea Bank. Unleash your tech creativity. Discover, collaborate, and bring to life innovative project ideas in various tech fields through this inspirational repository.
https://idea-arca.vercel.app
MIT License
8 stars 9 forks source link

Added my theme greeny #40

Closed baekusboo closed 12 months ago

baekusboo commented 12 months ago

Description

Added a new theme called greeny for the website!

Type of change

Screenshots

image
vercel[bot] commented 12 months ago

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

Name Status Preview Comments Updated (UTC)
idea-arca ✅ Ready (Inspect) Visit Preview 💬 Add feedback Oct 23, 2023 3:17pm
pull-request-quantifier-deprecated[bot] commented 12 months ago

This PR has 34 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

Quantification details

``` Label : Extra Small Size : +29 -5 Percentile : 13.6% Total files changed: 3 Change summary by file extension: .astro : +1 -0 .json : +20 -4 .scss : +8 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

pr-explainer-bot[bot] commented 12 months ago

Pull Request Report

Hey there! 👋 Here's a report on the recent pull request:

Changes

  1. Added a new option "Greeny" to the theme selector in ThemeSelector.astro file.

Suggestions to Improve Code

Bugs

Improvements

"tags": [
  "Python",
  "Natural Language Processing",
  "Machine Learning",
  "Flask"
],

Rating

I would rate the code a solid 8 out of 10. Here's a brief explanation of the criteria:

Keep up the good work! If you have any questions or need further assistance, feel free to reach out. 😄

sweep-ai[bot] commented 12 months ago

Apply Sweep Rules to your PR?

vizipi[bot] commented 12 months ago

Pull request analysis by VIZIPI

Below you will find who is the most qualified team member to review your code. This analysis includes his/her work on the code included in this Pull request, in addition to their experience in code affected by these changes ( partly found within the list of potential missing files below )   Feedback always welcome

Reviewers with knowledge related to these changes

Match % Person Commit Count Common Files
100.00 % Kumar Ashish Ranjan 10 3
66.67 % abhi7745 2 2
33.33 % NikhilOfficial07 5 1
33.33 % HardikPanwar 2 1
33.33 % s-bhalode 2 1
33.33 % Shu4bham 2 1

Potential missing files from this Pull request

files commonly committed with a subset of this pr, but not committed this time. (click to collapse)
FilePercentilerate
src/styles/global.scss50.00 %1 out of 2 times
src/database/sections.json50.00 %1 out of 2 times
src/pages/view/name/index.astro50.00 %1 out of 2 times
src/pages/view/name/id.astro50.00 %1 out of 2 times
README.md50.00 %1 out of 2 times
package-lock.json50.00 %1 out of 2 times
CONTRIBUTING.md50.00 %1 out of 2 times
src/styles/animations/stars.scss50.00 %1 out of 2 times
code_of_conduct.md50.00 %1 out of 2 times
.prettierrc.json50.00 %1 out of 2 times

Committed file ranks

  • 61.36%[src/components/ThemeSelector.astro]
  • 79.55%[src/styles/themes.scss]
  • 93.18%[src/database/MainData.json]