For this lab, I set up GitHub Actions in my ContextWeaver repo by creating a workflow file that runs pytest every time I push to main or open a pull request, and it was actually helpful because I could see right away when I broke something in scanner.py and when it got fixed. After that, I created a new branch and added more tests to my own project, then opened a PR to make sure CI was working properly.
For the partner part, I used rust-cli-tool repo, which was totally different from mine since it uses Rust and cargo test instead of Python and pytest. Writing a test in someone else’s project felt weird at first, but once I made a simple sanity test it was fine and it passed with their CI too.
Overall, setting up CI made me realize how useful it is because it catches mistakes right away, and it really does stop you from accidentally pushing broken code. The main CI setup and testing across repos went smoothly and now I understand why teams rely on this so much.
Top comments (0)