Aletia Trepte

@glenflorendo I documented changesets and found two ways to implement changesets into our work flow. We can change the release file or make two separate files, Version Workflow and Publish...

I completed parts 1 and 2 for issue #550: Create the release.yaml file in the correct directory. Trigger the workflow on pull requests merged into the stable branch. I'll research,...

Update: I've updated our project documentation to include details on how we're integrating Rush into our workflow using changesets. The changes aim to streamline our monorepo management, offering more efficient...

Update on issue #118, district types reusable tool: - Familiarization: I conducted a review of each target site so that I can understand the layout, available data, and challenges in...

Using the GeoHub L.A. website I programmatically created shape files: Data Acquisition: Utilizing the GeoHub LA website, I identified and accessed URL endpoints for the API calls corresponding to our...

Update: Data Acquisition, Extraction, Shapefile, and compression exploration can be accessed in my repo, [HERE](https://github.com/parcheesime/geohubLA_data_collection) This week I will look into how we can run the data collection script on...

Here's an update on data acquisition and extraction of district shape files: ### Update on the Shape File Automation Project - Implemented Google Drive functions to add files directly to...

Project Update: - A GitHub workflow has successfully been integrated to automatically update files in my Google Drive. - Adjustments made in main script to ensure compatibility with the GitHub...

This week I refined the setup of environment variables to enhance both local development and CI/CD workflows in GitHub Actions. By leveraging os.getenv() for securely accessing environment variables I've streamlined...

I gathered all the information for transferring my current repo with the District Shape File pipeline, into a new repo established in Hack for LA account for housing the shape...