Open
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changes are you trying to make?
I added and tested the data ingestion script (
assignment.sh) to automate file setup, organization, and cleanup.The script now creates required directories, moves and categorizes files, removes sensitive IP-related logs,
and generates an
inventory.txtfile that lists all processed data.What did you learn from the changes you have made?
I learned how to use shell commands such as
find,mv, andcpin combination with pattern matching,conditional directory creation, and file redirection. I also learned how to debug file path issues and verify directory outputs.
Was there another approach you were thinking about making?
I initially considered manually listing files for deletion and movement, but using pattern matching with
findproved to be more scalable and efficient.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
I faced issues with relative paths and ensuring files were being copied to the correct processed subfolders.
I overcame this by echoing intermediate steps and verifying each command’s output before finalizing the script.
How were these changes tested?
I ran
bash assignment.shmultiple times after deleting thenewprojectdirectory to confirm repeatability.I verified that all processed files were moved correctly, IP logs were deleted, and the inventory file was generated as expected.
A reference to a related issue in your repository (if applicable)
N/A
Checklist
Part 2: Merging Coworker Updates
What changes are you trying to make?
Pulled and merged coworker updates from the upstream repository to incorporate new features and ensure consistency with the shared base script.
What did you learn from the changes you have made?
I learned how to handle merge conflicts, review diffs carefully, and test my script after merging others’ changes to confirm full functionality.
Were there any challenges?
There were some conflicts in
assignment.shdue to overlapping file-handling logic. I resolved these by reviewing both sections and keeping the most efficient and logically correct code. I re-ran the script to verify it works as intended.How were these changes tested?
Re-ran
bash assignment.shmultiple times after deletingnewproject. Verified that files were properly categorized, sensitive data was removed, and the inventory file generated correctly.Checklist