Pull Request #749 by harmeetsingh11
feat: add reviewer assign github action workflow
Related issue:
This PR closes issue #739
Description: This pull request addresses the need for a GitHub Actions workflow that automates the process of assigning reviewers to pull requests upon their opening. Files added -
2. Reviewer Assignment Logic: Implement logic to automatically assign reviewers based on predefined rules or configurations defined in the workflow config. Expected Behavior: - The workflow triggers automatically when a pull request is opened. - Reviewers are assigned to the pull request based on the defined rules or configurations. - Reviewer assignments are 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] Implemented GitHub Actions workflow for automated reviewer assignment. - [X] Tested the workflow to ensure proper triggering and reviewer assignment. @pranshugupta54 please review this PR and don't forget to add SWOC and difficulty level label after merging the PR. Thanks <!-- This is an auto-generated comment: release notes by coderabbit.ai --> Summary by CodeRabbit - Chores - Implemented automation to streamline the review process by automatically assigning reviewers to pull requests. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Description: This pull request addresses the need for a GitHub Actions workflow that automates the process of assigning reviewers to pull requests upon their opening. Files added -
.github/workflows/action.yml
- .github/auto_assign.yml
Proposed Changes:
1. Workflow Development: Introduce a GitHub Actions workflow script that triggers upon the opening of a pull request.
2. Reviewer Assignment Logic: Implement logic to automatically assign reviewers based on predefined rules or configurations defined in the workflow config. Expected Behavior: - The workflow triggers automatically when a pull request is opened. - Reviewers are assigned to the pull request based on the defined rules or configurations. - Reviewer assignments are 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] Implemented GitHub Actions workflow for automated reviewer assignment. - [X] Tested the workflow to ensure proper triggering and reviewer assignment. @pranshugupta54 please review this PR and don't forget to add SWOC and difficulty level label after merging the PR. Thanks <!-- This is an auto-generated comment: release notes by coderabbit.ai --> Summary by CodeRabbit - Chores - Implemented automation to streamline the review process by automatically assigning reviewers to pull requests. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
19 Replies
Pull Request #768 by namnoum
fix: Issue 756 :Fix formatting and Input fields
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Added functionality to clear default text in input fields when focused for improved user experience.
- Style
- Updated input field placeholders and text capitalization for clarity.
- Adjusted styling for number inputs for better visual consistency.
- Refactor
- Reorganized component structure for enhanced readability and maintainability.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Pull Request #768 by namnoum
fix: Issue 756 :Fix formatting and Input fields
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Added functionality to clear default text in input fields when focused for improved user experience.
- Style
- Updated input field placeholders and text capitalization for clarity.
- Adjusted styling for number inputs for better visual consistency.
- Refactor
- Reorganized component structure for enhanced readability and maintainability.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Pull Request #771 by Swarga-codes
fix: loading page buttons
This PR basically provides a fix for the issue #728 in which there was a problem with the buttons in the loading screen component whose content was overflowing while the screen size was transitioning from medium screen size to phone screen size.
On fixing the css I could fix the overflowing issue and made it responsive for all screen sizes below is a screenshot of the fixed component.
!image
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- Style
- Updated the layout of buttons on the loading screen for improved alignment and spacing.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Pull Request #788 by Chaima-benyedder
fix: 783 Feature/implementing drawer closure upon clicking the blurred area
In the dashboard menu, when the screen is minimised pulling the drawer creates blurred content. When the drawer is closed the content remains blurred.
In the new code, this issue is fixed so that a simple click on the content unblurrs it.
This is a fix for this issue: https://github.com/digitomize/digitomize/issues/783
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Added a toggle feature to the user dashboard for improved navigation.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Pull Request #780 by youssefjaziri456
fixed bug (corrected the path to profile when clicking account)
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- Bug Fixes
- Corrected a typo in the routing declaration to ensure proper navigation within the app.
- New Features
- Updated navigation links: The "account" link in the dashboard now correctly points to the user's profile page.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Pull Request #771 by Swarga-codes
fix: loading page buttons
This PR basically provides a fix for the issue #728 in which there was a problem with the buttons in the loading screen component whose content was overflowing while the screen size was transitioning from medium screen size to phone screen size.
On fixing the css I could fix the overflowing issue and made it responsive for all screen sizes below is a screenshot of the fixed component.
!image
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- Style
- Updated the layout of buttons on the loading screen for improved alignment and spacing.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Unknown User•6mo ago
Message Not Public
Sign In & Join Server To View
Pull Request #1065 by imtahirabatool
syntax error in greeting.yml solved!
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- Chores
- Updated the GitHub Actions workflow to utilize a more general action reference, potentially enhancing its functionality and execution.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Pull Request #1065 by imtahirabatool
syntax error in greeting.yml solved!
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- Chores
- Updated the GitHub Actions workflow to utilize a more general action reference, potentially enhancing its functionality and execution.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Pull Request #1061 by mk0380
toast-repetition resolved
Pull Request Details
Description
This pull request resolves an issue where React toast messages were sometimes displayed several times in quick succession, giving users the impression they missed reading the first message or even spaming. The fix ensures that only one toast is visible at a time for each unique message content.
Fixes
Fixes #932
Type of PR
- [x] Bug fix
- [ ] Feature enhancement
- [ ] Documentation update
- [ ] Refactoring
- [ ] Other (specify): ___
Summary
Added a toastId for each toast, which assigns a unique ID each time a toast is generated, thus resolving the issue of multiple duplicate toasts appearing simultaneously.
#### Screenshots
Issue
!image
Resolved
!image
Additional Notes
- Tested thoroughly across different scenarios to ensure consistent behavior.
- Ensured compatibility with existing toast component configurations.
Checklist
- [x] I have read and followed the Pull Requests and Issues guidelines.
- [x] The code has been properly linted and formatted using
npm run lint:fix and npm run format:fix.
- [x] I have tested the changes thoroughly before submitting this pull request.
- [x] I have provided relevant issue numbers, snapshots, and videos after making the changes.
- [ ] I have not borrowed code without disclosing it, if applicable.
- [x] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
- [x] I have tested these changes locally.
- [x] My code follows the project's style guidelines.
- [ ] I have updated the documentation accordingly.
- [x] This PR has a corresponding issue in the issue tracker.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Enhanced toast notification functionality with unique identifiers for better user feedback across various components during actions like logout, sign-in, and community creation.
- Introduced a new utility function to generate unique toast identifiers.
- Bug Fixes
- Improved handling of toast notifications to prevent overlap and ensure distinct messaging.
- Documentation
- Updated internal documentation to reflect new functionality related to toast management.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->Pull Request #1052 by im-abdulmannan
fix: issue #1054 styling in dashboard career
Pull Request Details
Description
A minor change in styling of the card placed in user dashboard settings, where the user updates his/her skills
Fixes
[Cite any related issues or bugs that this PR addresses, e.g., "Fixes #issueNumber"]
This fixes is not specified to any issue created in the list, it is just enhancement of UI as seen in the ScreenShot
Type of PR
- [ ] Bug fix
- [x] Feature enhancement
- [ ] Documentation update
- [ ] Refactoring
- [ ] Other (specify): ___
Summary
[Summarize the changes made in this PR.]
Screenshots (if applicable)
[If your changes include UI updates, provide screenshots to illustrate the changes.]
Before:
!Screenshot from 2024-07-22 01-04-08
After:
!Screenshot from 2024-07-22 01-05-11
!image
Additional Notes
[Include any additional information or context that might be helpful for reviewers.]
Checklist
- [ ] I have read and followed the Pull Requests and Issues guidelines.
- [x] The code has been properly linted and formatted using
npm run lint:fix and npm run format:fix.
- [x] I have tested the changes thoroughly before submitting this pull request.
- [ ] I have provided relevant issue numbers, snapshots, and videos after making the changes.
- [ ] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
- [x] I have tested these changes locally.
- [x] My code follows the project's style guidelines.
- [ ] I have not borrowed code without disclosing it, if applicable.
- [ ] I have updated the documentation accordingly.
- [ ] This PR has a corresponding issue in the issue tracker.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Enhanced layout and responsiveness of the skills display in the dashboard.
- Bug Fixes
- Improved visual presentation of the skills section through updated styling.
- Refactor
- Simplified component dependencies by removing unnecessary imports.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->Pull Request #1068 by isonikrish
Added Blogs link to mobile navigation for portrait mode
Here's a detailed pull request template based on the issue with the missing "Blogs" link in the mobile navigation: #1056
---
Pull Request Details
Description
This pull request addresses the issue where the "Blogs" link was missing from the mobile navigation bar. The link has now been added to the list of navigation links so that users can easily access the blog section from mobile devices.
Fixes
Fixes the missing "Blogs" link in the mobile navigation bar.
Type of PR
- [x] Bug fix
Summary
- Added a new link for "Blogs" in the
navLinks array in the mobile navigation (MobNav) component.
- Ensured the link is consistent with the style and behavior of the other navigation links.
Additional Notes
No other significant changes were made apart from adding the missing link.
Checklist
- [x] I have read and followed the Pull Requests and Issues guidelines.
- [x] The code has been properly linted and formatted using npm run lint:fix and npm run format:fix.
- [x] I have tested the changes thoroughly before submitting this pull request.
- [x] I have provided relevant issue numbers, snapshots, and videos after making the changes.
- [x] I have not borrowed code without disclosing it, if applicable.
- [x] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
- [x] I have tested these changes locally.
- [x] My code follows the project's style guidelines.
- [x] I have updated the documentation accordingly.
- [ ] This PR has a corresponding issue in the issue tracker.
---
This template addresses the missing "Blogs" link issue. Let me know if you need to make any more changes!
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Introduced a "Blogs" section in the mobile navigation, providing direct access to external blog content.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->Pull Request #1065 by imtahirabatool
syntax error in greeting.yml solved!
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- Chores
- Updated the GitHub Actions workflow to utilize a more general action reference, potentially enhancing its functionality and execution.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
Pull Request #1068 by isonikrish
Added Blogs link to mobile navigation for portrait mode
Here's a detailed pull request template based on the issue with the missing "Blogs" link in the mobile navigation: #1056
---
Pull Request Details
Description
This pull request addresses the issue where the "Blogs" link was missing from the mobile navigation bar. The link has now been added to the list of navigation links so that users can easily access the blog section from mobile devices.
Fixes
Fixes the missing "Blogs" link in the mobile navigation bar.
Type of PR
- [x] Bug fix
Summary
- Added a new link for "Blogs" in the
navLinks array in the mobile navigation (MobNav) component.
- Ensured the link is consistent with the style and behavior of the other navigation links.
Additional Notes
No other significant changes were made apart from adding the missing link.
Checklist
- [x] I have read and followed the Pull Requests and Issues guidelines.
- [x] The code has been properly linted and formatted using npm run lint:fix and npm run format:fix.
- [x] I have tested the changes thoroughly before submitting this pull request.
- [x] I have provided relevant issue numbers, snapshots, and videos after making the changes.
- [x] I have not borrowed code without disclosing it, if applicable.
- [x] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
- [x] I have tested these changes locally.
- [x] My code follows the project's style guidelines.
- [x] I have updated the documentation accordingly.
- [ ] This PR has a corresponding issue in the issue tracker.
---
This template addresses the missing "Blogs" link issue. Let me know if you need to make any more changes!
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Introduced a "Blogs" section in the mobile navigation, providing direct access to external blog content.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->Pull Request #1062 by Uknowme-h
fix: issue #1056 -make 'Blogs' option visible in the navigation bar in portrait display
Pull Request Details
Description
fixed the issue #1056 , Made a minor change on the MobNav.jsx file
Fixes
fix: issue #1056 : make 'Blogs' option visible in the navigation bar in portrait display
Type of PR
- [+ ] Bug fix
- [ ] Feature enhancement
- [ ] Documentation update
- [ ] Refactoring
- [ ] Other (specify): ___
Summary
Added Blog title and path in the navLinks on this (client/src/components/globals/MobNav.jsx)
Screenshots (if applicable)
!image
Additional Notes
[Include any additional information or context that might be helpful for reviewers.]
Checklist
- [+ ] I have read and followed the Pull Requests and Issues guidelines.
- [+ ] The code has been properly linted and formatted using
- Style - Improved formatting of the JSX structure for better readability while preserving existing functionality. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
npm run lint:fix and npm run format:fix.
- [ +] I have tested the changes thoroughly before submitting this pull request.
- [ +] I have provided relevant issue numbers, snapshots, and videos after making the changes.
- [ +] I have not borrowed code without disclosing it, if applicable.
- [ +] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
- [+ ] I have tested these changes locally.
- [+ ] My code follows the project's style guidelines.
- [ ] I have updated the documentation accordingly.
- [+ ] This PR has a corresponding issue in the issue tracker.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Introduced a new "Blogs" navigation item, providing direct access to blog content.
- Style - Improved formatting of the JSX structure for better readability while preserving existing functionality. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Pull Request #1070 by Sahilll15
github integration
closes #1059
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Introduced a new
GithubProfile component to display a user's GitHub repositories.
- Updated routing to include the Github component for improved navigation.
- Bug Fixes
- Enhanced logout functionality with better state management and user feedback.
- Chores
- Transitioned Firebase configuration from environment variables to hardcoded values for improved stability.
- Removed obsolete environment variable configuration file.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->Pull Request #1069 by rasadregmi
Click Here Button Issue Solved
Pull Request Details
Description
I changed the Button.jsx component so that it can now redirect to the https://digitomize.com/contact page when the "Click Here" button is clicked.
Fixes
This PR addresses the issue of the button not functioning as expected by implementing the redirect functionality.
Type of PR
- [✓] Bug fix
- [ ] Feature enhancement
- [ ] Documentation update
- [ ] Refactoring
- [ ] Other (specify): ___
Summary
Updated the Button component to ensure it redirects to the contact page upon clicking.
Checklist
- [✓] I have read and followed the Pull Requests and Issues guidelines.
- [✓] The code has been properly linted and formatted using
npm run lint:fix and npm run format:fix.
- [✓] I have tested the changes thoroughly before submitting this pull request.
- [✓] I have provided relevant issue numbers, snapshots, and videos after making the changes.
- [✓] I have not borrowed code without disclosing it, if applicable.
- [✓] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
- [✓] I have tested these changes locally.
- [✓] My code follows the project's style guidelines.
- [✓] I have updated the documentation accordingly.
- [✓] This PR has a corresponding issue in the issue tracker.Pull Request #1068 by isonikrish
Added Blogs link to mobile navigation for portrait mode
Here's a detailed pull request template based on the issue with the missing "Blogs" link in the mobile navigation: #1056
---
Pull Request Details
Description
This pull request addresses the issue where the "Blogs" link was missing from the mobile navigation bar. The link has now been added to the list of navigation links so that users can easily access the blog section from mobile devices.
Fixes
Fixes the missing "Blogs" link in the mobile navigation bar.
Type of PR
- [x] Bug fix
Summary
- Added a new link for "Blogs" in the
navLinks array in the mobile navigation (MobNav) component.
- Ensured the link is consistent with the style and behavior of the other navigation links.
Additional Notes
No other significant changes were made apart from adding the missing link.
Checklist
- [x] I have read and followed the Pull Requests and Issues guidelines.
- [x] The code has been properly linted and formatted using npm run lint:fix and npm run format:fix.
- [x] I have tested the changes thoroughly before submitting this pull request.
- [x] I have provided relevant issue numbers, snapshots, and videos after making the changes.
- [x] I have not borrowed code without disclosing it, if applicable.
- [x] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
- [x] I have tested these changes locally.
- [x] My code follows the project's style guidelines.
- [x] I have updated the documentation accordingly.
- [ ] This PR has a corresponding issue in the issue tracker.
---
This template addresses the missing "Blogs" link issue. Let me know if you need to make any more changes!
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Introduced a "Blogs" section in the mobile navigation, providing direct access to external blog content.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->Pull Request #1067 by isonikrish
Fixed - Popup should be closed after user hit the save button! #1064
Here's a detailed pull request (PR) description following the structure you provided:
---
Pull Request Details
Description
Issue: The modal dialog was not closing after form submission.
Impact: Users were unable to close the dialog and continue using the application as intended.
Bug: The dialog was not closing because the state update logic was not properly handled or
Impact: Users were unable to close the dialog and continue using the application as intended.
Bug: The dialog was not closing because the state update logic was not properly handled or
handleClose was not being called correctly.
Fixes
Updated the dialog closure logic by replacing the handleClose function with direct setOpen(false) calls in the handleModalSubmit function and onClose prop of the Dialog component. This change ensures that the dialog closes immediately after form submission is processed and resolves issue #1064.
Type of PR
- [x] Bug fix
Summary
This PR addresses the issue where the modal dialog did not close after form submission. By updating the dialog closure logic to use setOpen(false) directly, the dialog now correctly closes upon form submission. The changes include:
- Directly using setOpen(false) in the handleModalSubmit function after handleSubmit completes.
- Setting the onClose prop of the Dialog component to () => setOpen(false) to handle closure from user interactions like clicking outside the dialog or pressing the escape key.
Additional Notes
- Testing: Ensure that the handleSubmit function properly handles errors to prevent issues where the dialog might close before submission is fully processed.
- Consistency: Verify that the dialog closure behavior is consistent across different user interactions and scenarios.
Checklist
- [x] I have read and followed the Pull Requests and Issues guidelines.
- [x] The code has been properly linted and formatted using npm run lint:fix and npm run format:fix.
- [x] I have tested the changes thoroughly before submitting this pull request.
- [x] I have provided relevant issue numbers, snapshots, and videos after making the changes.
- [x] I have not borrowed code without disclosing it, if applicable.
- [x] This pull request is not a Work In Progress (WIP), and only completed and tested changes are included.
- [x] I have tested these changes locally.
- [x] My code follows the project's style guidelines.
- [x] I have updated the documentation accordingly.
- [x] This PR has a corresponding issue in the issue tracker.
---
Feel free to adjust any parts of this template based on your specific changes or additional context.
<!-- This is an auto-generated comment: release notes by coderabbit.ai -->
Summary by CodeRabbit
- New Features
- Enhanced the PlatformModal component to ensure it closes only after the submission process is complete, improving user experience.
- Bug Fixes
- Resolved issues with premature modal closure during submission.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->