Issue #744 by dependabot[bot]
Bump husky from 8.0.3 to 9.0.11
Bumps husky from 8.0.3 to 9.0.11.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/typicode/husky/releases">husky's releases</a>.</em></p>
<blockquote>
<h2>v9.0.11</h2>
<ul>
<li>chore: update <code>package-lock.json</code> by <a href="https://github.com/btea"><code>@btea</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1383">typicode/husky#1383</a></li>
<li>fix: <code>export HUSKY=0</code> in init (fixes <a href="https://redirect.github.com/typicode/husky/issues/1393">#1393</a>) by <a href="https://github.com/typicode"><code>@typicode</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1395">typicode/husky#1395</a></li>
</ul>
<h2>v9.0.10</h2>
<ul>
<li>fix: rename index.d.ts to index.d.mts by <a href="https://github.com/mrkjdy"><code>@mrkjdy</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1379">typicode/husky#1379</a></li>
</ul>
<h2>v9.0.9</h2>
<ul>
<li>refactor: rename files by <a href="https://github.com/typicode"><code>@typicode</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1378">typicode/husky#1378</a></li>
</ul>
<h2>v9.0.8</h2>
<ul>
<li>docs: update index.md by <a href="https://github.com/khaledYS"><code>@khaledYS</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1369">typicode/husky#1369</a></li>
<li>Fix tab detection on install command by <a href="https://github.com/glensc"><code>@glensc</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1376">typicode/husky#1376</a></li>
<li>refactor: reduce file size by <a href="https://github.com/typicode"><code>@typicode</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1377">typicode/husky#1377</a></li>
</ul>
<h2>v9.0.7</h2>
<ul>
<li>fix: typo and source <code>~/.huskyrc</code> correctly (compatibility with v8)</li>
<li>docs: fix example by <a href="https://github.com/typicode"><code>@typicode</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1363">typicode/husky#1363</a></li>
</ul>
<h2>v9.0.6</h2>
<ul>
<li>docs: add favicon by <a href="https://github.com/rakleed"><code>@rakleed</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1354">typicode/husky#1354</a></li>
<li>chore: apply editorconfig to code only by <a href="https://github.com/typicode"><code>@typicode</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1355">typicode/husky#1355</a></li>
<li>docs: update install script to mjs and fix CI checks by <a href="https://github.com/starnayuta"><code>@starnayuta</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1357">typicode/husky#1357</a></li>
<li>Fix unbound variable by <a href="https://github.com/typicode"><code>@typicode</code></a> in <a href="https://redirect.github.com/typicode/husky/pull/1359">typicode/husky#1359</a></li>
</ul>
<h2>v9.0.5</h2>
<ul>
<li>docs: update path to ...
19 Replies
Issue #741 by JustFelix-Dev
Resolved Responsiveness Glitch
This PR;
- addresses the issue ticket #449
- fixes horizontal overflow issue
- adds gradient color and width to react fast marquee for a cooler effect
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- Style
- Updated layout and styling of contest cards for better alignment and visual appeal.
- Enhanced the marquee component with gradient effects for improved aesthetics.
- Adjusted the layout of a section on the home page for consistent width across devices.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Issue #740 by utkarsh4321
fix: Issue #468 REST API Integration for CodeChef: Retrieve Questions
Fix Issue #467
To fix this issue the following implementation takes place:
-
backend/users/controllers/userProfileController.js added checks for total, hard, medium and easy questions.
- Updated backend/users/controllers/platforms/codechefUpdater.js to retrieve total questions from the codechef profile page.
Screenshot of the DB:
For Codechef:
<img width="198" alt="image" src="https://github.com/digitomize/digitomize/assets/30936607/fb550a64-624a-4407-b14a-c836f37b67f8">
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Improved the accuracy of user information extraction for CodeChef and Codeforces platforms.
- Refactor
- Enhanced the logic for handling HTTPS requests and concurrent data fetching for better performance and reliability.
- Bug Fixes
- Ensured default values are set for question data in user profiles to prevent data inconsistencies.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->Issue #739 by harmeetsingh11
[Feature]: Implement Automatic Reviewer Assignment Workflow for Pull Requests
Is your feature request related to a problem? Please describe.
This issue addresses the need for a GitHub Actions workflow that automatically assigns reviewers to pull requests upon their opening. Automating the reviewer assignment process will streamline code review processes and ensure timely feedback from team members.
Proposed Feature:
The proposed feature involves the creation of a GitHub Actions workflow that triggers upon the opening of a pull request. This workflow will automatically assign designated reviewers based on predefined list of reviewers in the workflow config.
Expected Behavior:
- When a pull request is opened, the workflow should trigger automatically.
- Based on defined rules or configurations, reviewers will be assigned to the pull request.
- Reviewer assignments should be customizable and adaptable to project-specific requirements.
Benefits:
- Streamlines the code review process by automating reviewer assignments.
- Ensures timely feedback and reduces bottlenecks in the development workflow.
- Improves collaboration and accountability among team members.
Checklist
- [X] I have starred the repository
- [X] I agree to follow this project's Code of Conduct
- [X] I have checked the existing issues
- [X] I am willing to work on this issue
- [X] I am an SWOC 2024 contributor
Issue #730 by mayankbaranwal0
Made terminal logs colorful
Fixes #526
Enhanced terminal logs readability using picocolors by implementing a standard 4-color scheme
- Red for Errors & warnings
- Green for Successful outcome & task completion
- Yellow for Caution & debugging info
- Blue for Messages & general info
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- Refactor
- Enhanced server console output with color-coded formatting for better readability and distinction.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Issue #728 by SHUBH0924
[Bug]: Loading page button is not fixed
Contact Details
[email protected]
What happened?
In the loading page at the dashboard, buttons are not aligned with text properly.
!image
What browsers are you seeing the problem on?
Chrome, Brave, edge
Relevant log output
No response
Are you interested in contributing?
- [x] I'd like to work on this issue
Code of Conduct
- [X] I have used the search function to check if an issue already exists
- [X] I agree to follow this project's Code of Conduct
Issue #706 by dependabot[bot]
Bump concurrently from 8.2.1 to 8.2.2
Bumps concurrently from 8.2.1 to 8.2.2.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/open-cli-tools/concurrently/releases">concurrently's releases</a>.</em></p>
<blockquote>
<h2>v8.2.2</h2>
<h2>What's Changed</h2>
<ul>
<li>fix(suggestion): prefixColors API type to embrace string type by <a href="https://github.com/SeiwonPark"><code>@SeiwonPark</code></a> in <a href="https://redirect.github.com/open-cli-tools/concurrently/pull/439">open-cli-tools/concurrently#439</a></li>
<li>Update dependencies by <a href="https://github.com/paescuj"><code>@paescuj</code></a> in <a href="https://redirect.github.com/open-cli-tools/concurrently/pull/441">open-cli-tools/concurrently#441</a></li>
<li>Test against Node.js v20 instead of v19 by <a href="https://github.com/paescuj"><code>@paescuj</code></a> in <a href="https://redirect.github.com/open-cli-tools/concurrently/pull/442">open-cli-tools/concurrently#442</a></li>
<li>Update dependencies by <a href="https://github.com/paescuj"><code>@paescuj</code></a> in <a href="https://redirect.github.com/open-cli-tools/concurrently/pull/449">open-cli-tools/concurrently#449</a></li>
</ul>
<h2>New Contributors</h2>
<ul>
<li><a href="https://github.com/SeiwonPark"><code>@SeiwonPark</code></a> made their first contribution in <a href="https://redirect.github.com/open-cli-tools/concurrently/pull/439">open-cli-tools/concurrently#439</a></li>
</ul>
<p><strong>Full Changelog</strong>: <a href="https://github.com/open-cli-tools/concurrently/compare/v8.2.1...v8.2.2">https://github.com/open-cli-tools/concurrently/compare/v8.2.1...v8.2.2</a></p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/open-cli-tools/concurrently/commit/5a45482cbbc8bef74aef92770fc47e69abedcc54"><code>5a45482</code></a> 8.2.2</li>
<li><a href="https://github.com/open-cli-tools/concurrently/commit/e06501b0beaaaefe7a10011a1003956c4a62cb5f"><code>e06501b</code></a> Update dependencies (<a href="https://redirect.github.com/open-cli-tools/concurrently/issues/449">#449</a>)</li>
<li><a href="https://github.com/open-cli-tools/concurrently/commit/ac668c7ae7f56c0ffb8eb69d61a11a9e70c6391a"><code>ac668c7</code></a> logger: use subscribeSpyTo in tests</li>
<li><a href="https://github.com/open-cli-tools/concurrently/commit/a61ef39468c82b66ebb247a5a5e2cf479a0c4def"><code>a61ef39</code></a> Test against Node.js v20 instead of v19 (<a href="https://redirect.github.com/open-cli-tools/concurrently/issues/442">#442</a>)</li>
<li><a href="https://github.com/open-cli-tools/concurrently/commit/565e0b1684e40e83a1a8ce6088c8d16ccc796692"><code>565e0b1</code></a> Update dependencies (<a href="https://redirect.github.com/open-cli-tools/concurrently/issues/441">#441</a>)</li>
<li><a href="https://github.com/open-cli-tools/concurrently/commit/81529a97be1d5fb3577004bf538af43c97b5b164"><code>81529a9</code></a> fix(suggestion): prefixColors ...
Issue #704 by dependabot[bot]
Bump prettier from 3.1.0 to 3.2.5
Bumps prettier from 3.1.0 to 3.2.5.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/prettier/prettier/releases">prettier's releases</a>.</em></p>
<blockquote>
<h2>3.2.5</h2>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#325">Changelog</a></p>
<h2>3.2.4</h2>
<ul>
<li>Fix <code>.eslintrc.json</code> format <a href="https://redirect.github.com/prettier/prettier/issues/15947">#15947</a></li>
</ul>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#324">Changelog</a></p>
<h2>3.2.3</h2>
<ul>
<li>Format <code>tsconfig.json</code> file with <code>jsonc</code> parser <a href="https://redirect.github.com/prettier/prettier/issues/15927">#15927</a></li>
</ul>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#323">Changelog</a></p>
<h2>3.2.2</h2>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#322">Changelog</a></p>
<h2>3.2.1</h2>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#321">Changelog</a></p>
<h2>3.2.0</h2>
<p><a href="https://github.com/prettier/prettier/compare/3.1.1...3.2.0">diff</a></p>
<p>🔗 <a href="https://prettier.io/blog/2024/01/12/3.2.0.html">Release note</a></p>
<h2>3.1.1</h2>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#311">Changelog</a></p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md">prettier's changelog</a>.</em></p>
<blockquote>
<h1>3.2.5</h1>
<p><a href="https://github.com/prettier/prettier/compare/3.2.4...3.2.5">diff</a></p>
<h4>Support Angular inline styles as single template literal (<a href="https://redirect.github.com/prettier/prettier/pull/15968">#15968</a> by <a href="https://github.com/sosukesuzuki"><code>@sosukesuzuki</code></a>)</h4>
<p><a href="https://blog.angular.io/introducing-angular-v17-4d7033312e4b">Angular v17</a> supports single string inline styles.</p>
<!-- raw HTML omitted -->
<pre lang="ts"><code>// Input
@Component({
template:
<div>...</div>,
styles: h1 { color: blue; },
})
export class AppComponent {}
<p>// Prettier 3.2.4
<a href="https://github.com/Component"><code>@Component</code></a>({
template: <code>&lt;div&gt;...&lt;/div&gt;</code>,
styles: <code>h1 { color: blue; }</code>,
})
export class AppComponent {}</p>
<p>// Prettier 3.2.5
<a href="https://github.com/Component"><code>@Component</code></a>({
template: <code>&lt;div&gt;...&lt;/div&gt;</code>,
styles: <code>h1 { color: blue; }</code>,
})
export class AppComponent {}</p>
<p></code></pre></p>
<h4>Unexpected embedded formatting for Angular template (<a href="https://redirect.github.com/prettier/prettier/pull/15969">#15969</a> by <a href="https://github.com/JounQin"><code>@JounQin</code></a>)</h4>
<p>Computed template should not be considered as A...Issue #588 by jaydeep203
feature: Signup or Login modal added
Feature #532
I have created a login/signup modal in client/components/modals .
I have added it currently in the leaderboard section of the website; if the user is not logged in, it gets triggered in the useEffect hook. I have created a src/hooks/useLoginModal.ts file to control the open and close of the modal using zustand. Use the modal wherever you want in the app. I have not tested it in the backend because I only updated the frontend.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Introduced a modal component for user authentication and registration, supporting both traditional and social (Google, GitHub) login methods.
- Added a custom React hook for managing the visibility of the login modal.
- Chores
- Updated the
.gitignore file for better file management in version control.
- Enhancements
- Integrated the new authentication modal into the Leaderboard feature, prompting users to log in or register to view leaderboard details.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->Issue #581 by Manishak798
[Feature]: Re-designing of the Card and inserting API fetched User Details
Is your feature request related to a problem? Please describe.
As a viewer, these cards don't showcase any information at all that would help the visitors, we can consider restyling the card elements and to make it more readable we can insert dynamic card values through JS API or we can create our user API.
Describe the solution you'd like
By using javascript and CSS for this we can achieve desired results for the same.
Alternatives
No response
Additional Context
!Screenshot 2024-01-28 170013
Are you interested in contributing?
- [ ] I'd like to work on this issue
Code of Conduct
- [X] I have used the search function to check if an issue already exists
- [X] I agree to follow this project's Code of Conduct
Issue #580 by Manishak798
[Feature]: Redesigning of this user Card
Is your feature request related to a problem? Please describe.
Re-Designing this to create a new user card will make the website look more appealing to the users.
Describe the solution you'd like
The solution to this is to do restyling of elements and adding js to the input tag to remove their input value when the page refreshes.
Alternatives
As a SWOC mentor, I am raising this issue for contributors.
Additional Context
!Screenshot 2024-01-28 165927
Are you interested in contributing?
- [ ] I'd like to work on this issue
Code of Conduct
- [X] I have used the search function to check if an issue already exists
- [X] I agree to follow this project's Code of Conduct
Issue #566 by Ajen07
feat: Send verification email
fixes #538
It sends verification email to users signingup using email and password using firebase
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Enhanced email verification process, including the ability to resend verification emails.
- Added toast notifications for successful actions.
- Updated authentication flow to include email verification checks.
- Bug Fixes
- Improved password visibility toggle functionality.
- Refactor
- Updated navigation and authentication logic across several components for a smoother user experience.
- Style
- Introduced new styles for the email verification components, ensuring responsive design.
- Chores
- Minor UI adjustments and comment updates for clarity.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Issue #538 by pranshugupta54
[Bug]: Email verification on signup
Contact Details
No response
What happened?
There is no verification when user signs up using email
- Use email verification with firebase - info.
- Also implement a check for all authorised page to redirect to login page with message as "Verify your email address first"
What browsers are you seeing the problem on?
No response
Relevant log output
No response
Are you interested in contributing?
- [ ] I'd like to work on this issue
Code of Conduct
- [X] I have used the search function to check if an issue already exists
- [X] I agree to follow this project's Code of Conduct
Issue #537 by pranshugupta54
[Feature]: Programs section on About Page
Is your feature request related to a problem? Please describe.
include program list like swoc kwoc etc
Describe the solution you'd like
On the about page, make a section for programs using react marquee, which shows all the programs we're a part of.
- KWOC
- SWOC
- Tublian
- IWOC
Alternatives
No response
Additional Context
Include their images (prefer svg) and date below it.
Are you interested in contributing?
- [ ] I'd like to work on this issue
Code of Conduct
- [X] I have used the search function to check if an issue already exists
- [X] I agree to follow this project's Code of Conduct
Issue #536 by Parmesh119
[Feature]: Contact Us page in official website
Is your feature request related to a problem? Please describe.
In this official website, there is a contact us page but the contact us page doesn't exist.
Describe the solution you'd like
I would like to make the new contact us form with already mentioned information in website.
Alternatives
No response
Additional Context
No response
Are you interested in contributing?
- [X] I'd like to work on this issue
Code of Conduct
- [X] I have used the search function to check if an issue already exists
- [X] I agree to follow this project's Code of Conduct
Issue #1038 by dependabot[bot]
Bump the npm_and_yarn group across 3 directories with 4 updates
Bumps the npm_and_yarn group with 3 updates in the /backend directory: @grpc/grpc-js, braces and ws.
Bumps the npm_and_yarn group with 4 updates in the /client directory: @grpc/grpc-js, braces, ws and engine.io-client.
Bumps the npm_and_yarn group with 2 updates in the /extension/contest_list directory: braces and ws.
Updates
@grpc/grpc-js from 1.10.7 to 1.10.9
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/grpc/grpc-node/releases"><code>@grpc/grpc-js</code>'s releases</a>.</em></p>
<blockquote>
<h2><code>@grpc/grpc-js</code> 1.10.9</h2>
<ul>
<li>Avoid buffering significantly more than <code>grpc.max_receive_message_size</code> per received message.</li>
</ul>
<h2><code>@grpc/grpc-js</code> 1.10.8</h2>
<ul>
<li>Fix a bug that caused channels with <code>unix:</code> targets to not reconnect after the channel goes idle (<a href="https://redirect.github.com/grpc/grpc-node/issues/2750">#2750</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/grpc/grpc-node/commit/674f4e351a619fd4532f84ae6dff96b8ee4e1ed3"><code>674f4e3</code></a> Merge pull request from GHSA-7v5v-9h63-cj86</li>
<li><a href="https://github.com/grpc/grpc-node/commit/7ecaa2d2dcaaa49467d41143169212caf55a40cd"><code>7ecaa2d</code></a> grpc-js: Bump to 1.10.9</li>
<li><a href="https://github.com/grpc/grpc-node/commit/e64d816d7df6d6cde62314beb67d11f1e0a8c79e"><code>e64d816</code></a> grpc-js: Avoid buffering significantly more than max_receive_message_size per...</li>
<li><a href="https://github.com/grpc/grpc-node/commit/45e5fe5462fea6cb4e3898fa2f07a4836f95916a"><code>45e5fe5</code></a> Merge pull request <a href="https://redirect.github.com/grpc/grpc-node/issues/2750">#2750</a> from murgatroid99/grpc-js_idle_uds_fix</li>
<li><a href="https://github.com/grpc/grpc-node/commit/87a35414021f627f01591cade9b1f9a7dcaaf5d3"><code>87a3541</code></a> grpc-js: Fix UDS channels not reconnecting after going idle</li>
<li><a href="https://github.com/grpc/grpc-node/commit/3105791fbe8a615a28289da33ad584fb868d2ff6"><code>3105791</code></a> Merge pull request <a href="https://redirect.github.com/grpc/grpc-node/issues/2740">#2740</a> from sergiitk/backport-1.10-psm-interop-common-prod-...</li>
<li><a href="https://github.com/grpc/grpc-node/commit/fec135a9800ce884b8dd414782f4bd0014821a0c"><code>fec135a</code></a> Merge pull request <a href="https://redirect.github.com/grpc/grpc-node/issues/2729">#2729</a> from sergiitk/psm-interop-common-prod-tests</li>
<li><a href="https://github.com/grpc/grpc-node/commit/76fe802309ff39c79887d494760de25633b2beb1"><code...Issue #1037 by dependabot[bot]
Bump the npm_and_yarn group across 3 directories with 3 updates
Bumps the npm_and_yarn group with 2 updates in the /backend directory: @grpc/grpc-js and ws.
Bumps the npm_and_yarn group with 3 updates in the /client directory: @grpc/grpc-js, ws and engine.io-client.
Bumps the npm_and_yarn group with 1 update in the /extension/contest_list directory: ws.
Updates
@grpc/grpc-js from 1.10.7 to 1.10.9
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/grpc/grpc-node/releases"><code>@grpc/grpc-js</code>'s releases</a>.</em></p>
<blockquote>
<h2><code>@grpc/grpc-js</code> 1.10.9</h2>
<ul>
<li>Avoid buffering significantly more than <code>grpc.max_receive_message_size</code> per received message.</li>
</ul>
<h2><code>@grpc/grpc-js</code> 1.10.8</h2>
<ul>
<li>Fix a bug that caused channels with <code>unix:</code> targets to not reconnect after the channel goes idle (<a href="https://redirect.github.com/grpc/grpc-node/issues/2750">#2750</a>)</li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/grpc/grpc-node/commit/674f4e351a619fd4532f84ae6dff96b8ee4e1ed3"><code>674f4e3</code></a> Merge pull request from GHSA-7v5v-9h63-cj86</li>
<li><a href="https://github.com/grpc/grpc-node/commit/7ecaa2d2dcaaa49467d41143169212caf55a40cd"><code>7ecaa2d</code></a> grpc-js: Bump to 1.10.9</li>
<li><a href="https://github.com/grpc/grpc-node/commit/e64d816d7df6d6cde62314beb67d11f1e0a8c79e"><code>e64d816</code></a> grpc-js: Avoid buffering significantly more than max_receive_message_size per...</li>
<li><a href="https://github.com/grpc/grpc-node/commit/45e5fe5462fea6cb4e3898fa2f07a4836f95916a"><code>45e5fe5</code></a> Merge pull request <a href="https://redirect.github.com/grpc/grpc-node/issues/2750">#2750</a> from murgatroid99/grpc-js_idle_uds_fix</li>
<li><a href="https://github.com/grpc/grpc-node/commit/87a35414021f627f01591cade9b1f9a7dcaaf5d3"><code>87a3541</code></a> grpc-js: Fix UDS channels not reconnecting after going idle</li>
<li><a href="https://github.com/grpc/grpc-node/commit/3105791fbe8a615a28289da33ad584fb868d2ff6"><code>3105791</code></a> Merge pull request <a href="https://redirect.github.com/grpc/grpc-node/issues/2740">#2740</a> from sergiitk/backport-1.10-psm-interop-common-prod-...</li>
<li><a href="https://github.com/grpc/grpc-node/commit/fec135a9800ce884b8dd414782f4bd0014821a0c"><code>fec135a</code></a> Merge pull request <a href="https://redirect.github.com/grpc/grpc-node/issues/2729">#2729</a> from sergiitk/psm-interop-common-prod-tests</li>
<li><a href="https://github.com/grpc/grpc-node/commit/76fe802309ff39c79887d494760de25633b2beb1"><code>76fe802</code></a> Merge pull request <a href="https://redirect.github.com/grpc/grpc-node/issues/2739">#2739</a> from murgatroid99/backport-1.10-gr...Issue #1035 by dependabot[bot]
Bump prettier from 3.1.0 to 3.3.2
Bumps prettier from 3.1.0 to 3.3.2.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/prettier/prettier/releases">prettier's releases</a>.</em></p>
<blockquote>
<h2>3.3.2</h2>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#332">Changelog</a></p>
<h2>3.3.1</h2>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#331">Changelog</a></p>
<h2>3.3.0</h2>
<p><a href="https://github.com/prettier/prettier/compare/3.2.5...3.3.0">diff</a></p>
<p>🔗 <a href="https://prettier.io/blog/2024/06/01/3.3.0.html">Release note</a></p>
<h2>3.2.5</h2>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#325">Changelog</a></p>
<h2>3.2.4</h2>
<ul>
<li>Fix <code>.eslintrc.json</code> format <a href="https://redirect.github.com/prettier/prettier/issues/15947">#15947</a></li>
</ul>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#324">Changelog</a></p>
<h2>3.2.3</h2>
<ul>
<li>Format <code>tsconfig.json</code> file with <code>jsonc</code> parser <a href="https://redirect.github.com/prettier/prettier/issues/15927">#15927</a></li>
</ul>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#323">Changelog</a></p>
<h2>3.2.2</h2>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#322">Changelog</a></p>
<h2>3.2.1</h2>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#321">Changelog</a></p>
<h2>3.2.0</h2>
<p><a href="https://github.com/prettier/prettier/compare/3.1.1...3.2.0">diff</a></p>
<p>🔗 <a href="https://prettier.io/blog/2024/01/12/3.2.0.html">Release note</a></p>
<h2>3.1.1</h2>
<p>🔗 <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md#311">Changelog</a></p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/prettier/prettier/blob/main/CHANGELOG.md">prettier's changelog</a>.</em></p>
<blockquote>
<h1>3.3.2</h1>
<p><a href="https://github.com/prettier/prettier/compare/3.3.1...3.3.2">diff</a></p>
<h4>Fix handlebars path expressions starts with <code>@</code> (<a href="https://redirect.github.com/prettier/prettier/pull/16358">#16358</a> by <a href="https://github.com/Princeyadav05"><code>@Princeyadav05</code></a>)</h4>
<!-- raw HTML omitted -->
<pre lang="hbs"><code>{{! Input }}
<div>{{@x.y.z}}</div>
<p>{{! Prettier 3.3.1 }}
<div>{{<a href="https://github.com/x"><code>@x</code></a>}}</div></p>
<p>{{! Prettier 3.3.2 }}
<div>{{<a href="https://github.com/x"><code>@x</code></a>.y.z}}</div>
</code></pre></p>
<h1>3.3.1</h1>
<p><a href="https://github.com/prettier/prettier/compare/3.3.0...3.3.1">diff</a></p>
<h4>Preserve empty lines in front matter (<a href="https://redirect.github.com/prettier/prettier/pull/16347">#16347</a> by <a href="https://github.com/fisker"><code>@fisker</code></a>)</h4>
<!-- raw HTML omitted -->...
Issue #1034 by AkhilaSunesh
[Feature]: Add facility to view the password
Is your feature request related to a problem? Please describe.
!image
Location: Login and sign up page
Makes it easy for the users to view the password
Describe the solution you'd like
Professional outlook
Alternatives
No response
Additional Context
No response
Are you interested in contributing?
- [X] I'd like to work on this issue
Code of Conduct
- [X] I have used the search function to check if an issue already exists
- [X] I agree to follow this project's Code of Conduct
Which program are you contributing in?
gssoc
Issue #1033 by thevijayshankersharma
[Feature]: Automatic Comment on Pull Request Raised
Is your feature request related to a problem? Please describe.
Often, when pull requests (PRs) are raised, reviewers may lack crucial context about the changes proposed. This can lead to delays in the review process and misunderstandings between contributors and reviewers.
Describe the solution you'd like
I propose implementing an automatic commenting system that triggers whenever a new PR is raised. This system would generate a predefined comment containing essential context about the changes, such as the purpose of the modifications, relevant issue or feature IDs, and specific instructions for reviewers.
Alternatives
One alternative could be relying solely on manual comments by reviewers upon PR creation. However, this approach may be time-consuming and inconsistent across different reviewers. Another option could be not providing any initial comments on PRs, but this would result in contributors having to repeatedly provide context to reviewers, slowing down the review process.
Additional Context
Automating the commenting process upon PR creation would streamline the review process, improve communication between contributors and reviewers, and ultimately enhance the efficiency and effectiveness of our project's development workflow.
Are you interested in contributing?
- [X] I'd like to work on this issue
Code of Conduct
- [X] I have used the search function to check if an issue already exists
- [X] I agree to follow this project's Code of Conduct
Which program are you contributing in?
gssoc, ssoc