Skip to main content

Featured

Week 12: Release 0.4 Part: 3

Release 0.4 Part 3 This is going to be my final post for this class which covers my final update on my Release 0.4. Earlier this week I made a PR that ports SearchBar to NextJS but I'm still waiting for it to be reviewed some more. I've had some feedback that I have implemented and have also requested a review again. Overall this Release went pretty smoothly for the actually GitHub side of things like setting up the issue, making the PR, and so on. In Release 0.3 I wasn't so certain on how this process happened with Telescope, but now I never had these issues for 0.4. Issue #1470 Fix #1470: Port SearchBar from Gatsby -> NextJS #1503 Did I Meet My Goals? Going into this release I had two main goals: 1. Setup the Issue/PR with no issues 2. Learn about NextJS I feel like I meet both of these goals at the end. I had no issues setting up my branch, updating my master, making the issue, making the PR, and following through on review comments so far. When it comes to learning m

Week 5: PR#2

  Release 0.2: Pull Request #2

For the first PR, I worked on adding some new documentation to a project with adding the .editorconfig file, this time I wanted to work on some actual code. I found the PyLot repository which is a web based IDE for writing ETL pipelines in Python.

The maintainer had opened an issue wanting the randomlmao() function to be renamed to something appropriate to its function in camel case naming style. The first thing I did was look through the project at where this function connected to and from. I renamed the function and then updated the function calls throughout the project to use the new name. Once my changes were made I tested that the program still ran with the output it had before my changes were introduced.

All my work was done on my own fork using a new branch which was called mstewardson/issue-7. I pushed up my changes to my origin, and then made a PR to upstream. 

- Issue-7

- Pull Request (0bfc033)

Comments

Popular Posts