Create workflow for auto update experience table with gitauto model

gitauto-ai[bot] commented 3 months ago

Original issue: #112

What is the feature

This feature involves creating a workflow to automatically update the experience table in the index.html file using data from a JSON file in the README repository.

Why we need the feature

Automating the update process for the experience table ensures that the information remains current without requiring manual intervention. This reduces the risk of outdated information and streamlines the maintenance process.

How to implement and why

Download the JSON:
- Use a GitHub Action to download the JSON file containing the experience data from the README repository.
- This ensures that we always have the latest data available for updating the experience table.
Run the JS file:
- Execute a JavaScript file that processes the downloaded JSON and formats it appropriately for insertion into the index.html file.
- This step is crucial for transforming the raw data into a format that can be directly used in the HTML.
Replace content in index.html:
- Use the action to replace the existing experience table content in the index.html file with the newly formatted data.
- This ensures that the index.html file is updated with the latest experience information.
Commit the file:
- Commit the updated index.html file back to the repository.
- This step is necessary to save the changes and make them available for deployment.
Deploy:
- Deploy the updated index.html file to the live environment.
- This final step ensures that the changes are reflected on the live site, providing users with the most up-to-date experience information.

By following these steps, we can automate the process of updating the experience table, ensuring accuracy and saving time.

Test these changes locally

git checkout -b gitauto/issue-#112-548db01a-db86-465d-902e-526a9f524c30
git pull origin gitauto/issue-#112-548db01a-db86-465d-902e-526a9f524c30

socket-security[bot] commented 3 months ago

New dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/calculate-age@1.0.0	None	`0`	7.04 kB	arvindkumar.b
npm/chunk@0.0.3	None	`0`	3.76 kB	ryancole

View full report↗︎

socket-security[bot] commented 3 months ago

👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎

This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored.

Ignoring: npm/calculate-age@1.0.0

View full report↗︎

Next steps

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all