9/13/2023 0 Comments Github pull request meaning![]() Goal #3: How to handle cookies (my limited knowledge about secury led me to simply pass tokens using a cookie).Goal #2: How to use its "develop mode".This is actually the most important one, because I wanted to have the Github Secret Key hidden in one of these Variables. Goal #1: How to use Environment Variables.I had some reads about how use Netlify Functions to accomplish specific goals: The create-react-app CLI was my guy and made me forget all my setup problems I had some time ago while following some tutorials that are well explained but I guess I am not that smart. I was surprised how easy is to create a brand new web application and get it running. Meaning: Reading Pull Requests from the API was viable. Github API (Preliminary Research)įirst of all, I had to do some research about how to consume Github API, there are some previous articles I posted about it:īy doing that, I was able to confirm if what I wanted to do was possible. I literally just googled "github css styles" and found this cool thing that saved me a lot of time. I didn't want to spend time styling this web application. That is why I decided to go with Netlify Functions, which doesn't have that kind of restrictions and it's free, at least for this small project that won't have too much calls, I said "it's good". My first option was to create a Java or NodeJS service and deploy it on Heroku, but I didn't want to pay for this to be "live" forever (no sleep time). I was not sure which service and programming language to choose. I needed a backend service to hide the Secret Key to make calls to Github API. I am not a frontend guy, but I had some little projects (mostly TODO apps) that I had built previously and this time I wanted to create something "more elaborated" and get a better understanding of the basics.Ī must if I wanted to read data from Github Here is the summary of what I got and why: The Stack It was the time to choose the stack and tools to develop this web application. There are some more "features" I included in this project for different reasons, like Authentication (for obvious reasons), a search form, and some basic filtering functionality. Counts for current reviewer who: approved, requested changes, commented, awaiting within each pull request.Make use of Github API to read my pull requests based on my username and show valuable information within a web application. Official Github Pull Requests View looks like this:Ī different way to see the list of pull requests that could give me a better visibility of which code reviews I have in my queue and need my attention. Yeah, I know it's only one click away from seeing all of that, but as I was about to study the Github API, I decided to give it a try.īefore going to the details, I want to start showing two images that somewhat explains what is this all about. Like for example, the number of approvals each PR already have, or if there is already activity such comments, requested changes, and who did which action, so with all these information in that same list I can have a clearer idea what's going on there. Meaning, more than likely I have to visit frequently to see whichh PRs I have in my queue.Īfter some time seeing my list of PRs, I noticed there are cases where I would like to see more information in that list before clicking on one of those. ![]() Code Reviews with Pull Request, which is one of the features Github has, where you can interact with who owns the code changes before merging a branch into master.Īs a reviewer, I have to open pull requests regularly to do my review. That means, I had to get familiar with the tools this platform provides. I am maintaining a software that its repo is in Github. How I built a pull request viewer using Github API. : Project Github Pull Request Viewer Home |
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |