You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Title: feat: Implement CI/CD and monitoring workflows
Closes: #158
Description
This Pull Request introduces a comprehensive set of GitHub Actions workflows to automate key aspects of the development lifecycle, fulfilling the requirements of issue #158.
The following changes have been implemented:
Render Deployment Workflow (render-deploy.yml): A new workflow has been added to automatically trigger a deployment on Render via a deploy hook whenever changes are pushed to the main branch.
Enhanced Security Workflow (security.yml): The existing dependency.yml has been renamed to security.yml for improved clarity. The workflow has been enhanced to include a CodeQL Analysis job, which performs static code analysis to identify potential vulnerabilities, supplementing the existing npm audit job.
Performance Monitoring Workflow (performance-monitoring.yml): A new workflow has been added to execute a Lighthouse audit against the deployed frontend and backend URLs. This is scheduled for a weekly run and can also be triggered manually to ensure the project adheres to high performance, accessibility, and SEO standards.
Filesize Monitoring Workflow (filesize-monitor.yml): A new workflow has been created to calculate and report the file sizes of static assets within the public/ directory. This process runs on every Pull Request to prevent the unintentional introduction of large assets.
Additional Context
The project's README.md file was found to be slightly outdated regarding the directory structure. This implementation is based on the current structure of the repository, such as using the public/ directory for frontend assets.
Are you contributing under any open-source program?
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.
Hey @ojha13291 good work with that other PR, meanwhile solve these merge conflicts as well
hey i am not able to resolve the merge conflicts cause it is always showing some conflicts so i am thinking of abandoning it and working on another issue .
Hey @ojha13291 good work with that other PR, meanwhile solve these merge conflicts as well
hey i am not able to resolve the merge conflicts cause it is always showing some conflicts so i am thinking of abandoning it and working on another issue .
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ojha13291
force-pushed
the
feat/add-ci-workflows
branch
from
Title:
feat: Implement CI/CD and monitoring workflowsCloses:
#158Description
This Pull Request introduces a comprehensive set of GitHub Actions workflows to automate key aspects of the development lifecycle, fulfilling the requirements of issue #158.
The following changes have been implemented:
Render Deployment Workflow (
render-deploy.yml): A new workflow has been added to automatically trigger a deployment on Render via a deploy hook whenever changes are pushed to themainbranch.Enhanced Security Workflow (
security.yml): The existingdependency.ymlhas been renamed tosecurity.ymlfor improved clarity. The workflow has been enhanced to include a CodeQL Analysis job, which performs static code analysis to identify potential vulnerabilities, supplementing the existingnpm auditjob.Performance Monitoring Workflow (
performance-monitoring.yml): A new workflow has been added to execute a Lighthouse audit against the deployed frontend and backend URLs. This is scheduled for a weekly run and can also be triggered manually to ensure the project adheres to high performance, accessibility, and SEO standards.Filesize Monitoring Workflow (
filesize-monitor.yml): A new workflow has been created to calculate and report the file sizes of static assets within thepublic/directory. This process runs on every Pull Request to prevent the unintentional introduction of large assets.Additional Context
The project's
README.mdfile was found to be slightly outdated regarding the directory structure. This implementation is based on the current structure of the repository, such as using thepublic/directory for frontend assets.Are you contributing under any open-source program?
GirlScript Summer of Code 2025 (GSSoC'25)